The world of API architecture and development is tricky in many ways. Unfortunately, there is no such thing as a “perfect” solution, and with every new implementation or solution, new problems are bound to crop up.
It is important to remember, then, that even the most positive, powerful decisions in API architecture could have significant issues in the long run that, if not recognized in the hazy glow of post-adoption euphoria, could easily interfere with the success of an API or collection of APIs. Read more
An API is only as good as it is known. Getting an API into a developer’s hands, demonstrating the power of your solution, and providing an environment in which they can test and manipulate data in a controlled, monitored way is perhaps one of the most important unsung heroes of API publication. Read more
GraphQL is incredibly powerful — so powerful, in fact, that it is used by corporations such as Facebook to drive their large, complex social systems for billions of users. Despite this, the language is still relatively nascent, and its usage has yet to reach the dizzying heights that those languages it replaces and augments occupy. Read more
RESTful design is akin to the graphical user interface on modern computers — ubiquitous enough to be considered the de facto choice, but in practice, not necessarily the only option. REST is certainly considered by many to be the king of the hill, but it’s wrong to think it’s the only player in town. Read more
As bot technology evolves and migrates into the API space, many API practitioners are left asking — “what does this mean for our industry?” It’s an interesting question and intellectual experiment to undertake, and one that is heavily rooted in futurism. Read more