API styles are a topic of much contention. Most API practitioners are familiar with the REST vs. GraphQL debate, but that’s not to mention the countless other styles out there. The good news is that there is a simple, objective process for narrowing down the best style (or styles) for your next API project. Read more
While no two APIs are exactly the same, they do tend to share a lot of characteristics, from design features to data formats. Looking closely at these traits allows us to identify distinct types of APIs, which we can use to set clear expectations, discuss what does (and doesn’t) work, and stick to relevant best practices. Read more
At first glance, it would seem that the API space has embraced unified design standards. RESTful development uses HTTP to communicate between a client and a server. OpenAPI Spec serves to extend REST APIs, improving documentation and making APIs machine-friendly.
However, with just a little digging, it becomes apparent that this isn’t always the case. Read more
Web services and APIs are two of those overlapping tech terms that regularly get confused. You might have even heard these words used interchangeably, but are they even the same thing?
While they do have some overlap, web services and APIs are two different concepts. Read more
Serverless, GraphQL, Go, microservices… disruptive tech offers great benefits, but is “boring” tech better from a pragmatic viewpoint?
If it ain’t broke, don’t fix it. No need to reinvent the wheel. The KISS (Keep It Simple, Stupid!) principle. There are plenty of expressions and the like out there that advocate embracing the tried and tested over the complex and newfangled, but sometimes the siren song of cutting-edge technology is just too much to resist. Read more
