So much choice, when building a new API. Which architectural style should we choose for our cool new API? Are there any best practices regarding the architectural style for APIs? But first, what is an architectural style? In general, an
Any API needs to fulfill its responsibilities, such as gathering, structuring, delivering and securing data. But this is not enough to make the API really desirable for API consumers. What are the desirable properties of APIs? Desirability can be regarded
Jeff Bezos, Amazon founder and CEO, wrote the following memo to his employees around 2002. It got known as the “Bezos API Mandate” or “Amazon’s API Mandate”.
Let’s study the behavior of Alexa. Imagine the user says ”Alexa, what is the weather?” Now, which components of Alexa’s technical architecture are involved and how do they interact? In the following diagram, we give an overview of the involved
Let’s explore some common use cases for AWS AppSync, where AWS AppSync can help to build GraphQL APIs fast. Simple Data-Centric GraphQL API A typical use-case for AppSync is providing a data-centric API to an existing data source. The advantage
GraphQL is great but requires the manual installation and maintenance of software infrastructure components, tedious configuration, and some manual tweaking. And when running a productive GraphQL system, you need to find a way to scale the system up and down
So you are implementing your webhooks? Sweet. Then you have certainly asked yourself about the best way to test your webhook.
Let’s have a look at the AppSync architecture. In the figure below we have depicted such a high-level solution architecture for an app, an AppSync API and AWS data sources. On the left-hand side we have the clients connecting to
In general, API architecture spans the bigger picture of APIs and can be seen from several perspectives: API architecture may refer to the architecture of the complete solution, consisting not only of the API itself, but also of an API
In the API space, everybody is talking about REST. But really, why should APIs be RESTful? Great products are designed with rigorous customer focus, a deep understanding of the customers, their needs and desires. And with these ingredients, great customer