Systems | Development | Analytics | API | Testing

Let’s face it: In today’s modern world of cloud and containers, there are still thousands of legacy applications that were not written with an API-first approach. Some legacy systems can still provide tremendous value today, but the means for accessing them are completely out of date, thus rendering them almost useless.

There are two types of Ruby Begin and End blocks. A simple Google search of “Ruby begin end blocks” will lead you to either of these two kinds of articles – the ones in all caps (BEGIN and END) and the ones usually separated by a slash (begin/end). Both of these are different things but confused with the same name. In this post, we will dive into both. Here’s an outline of what we’ll be covering so you can easily navigate or skip ahead in the guide –

The RESTful web API has long been the industry standard, but in recent years, APIs based on the GraphQL Schema Definition Language has grown in popularity. This post will go over the advantages and disadvantages of each, as well as when GraphQL makes sense for your application.

Sometimes I walk through the grocery store and marvel at the way customers float through the aisles, blissfully unaware of the logistical nightmare it probably took to stock the shelves. They have no idea how many people, systems, and modes of transportation it takes to make everything magically appear on their grocery shelves. But I do. As the Senior Director of Software Engineering at KlearNow, I spend my days preserving the bliss of those grocery shoppers.