|Blog

In this talk, we will explore the process of building a Supergraph, a GraphQL schema that merges multiple sub-schemas, with the assistance of ChatGPT, an AI-powered chatbot engine. We will discuss how leveraging AI tools like ChatGPT can expedite the creation of prototypes.

APIs are an interesting topic, especially from a security perspective. Consider what an API is designed to enable. An application can communicate and exchange data with another application, including over the public Internet. By its very nature, an API must be publicly accessible. This makes APIs especially vulnerable to attack.

Designing APIs is a critical activity in many software projects. Its success depends upon requirements and the experience of the API designers. Pattern collections document collective experiences, making it possible to arrive at suitable designs quickly and with less risk. Join us on a short journey through microservices API patterns that look at protocol-independent problems in API design and propose proven solutions in a compact manner.

This article shows why it is extremely important to conduct API design reviews before interfaces go live.

When running one or multiple services, it is essential that they have reliable service contracts defining their exposed APIs. Those contracts mostly consist of declarative interface definitions, which strongly define and type the API exposed by the respective service. As such, it is crucial that the code making up the service exactly implements the interface and therefore fulfills its side of the contract. Regressions need to be detected and changes reflected in a well-communicated update to the contract. Here, we want to look at different ways of specifying contracts for what is one of the most common protocols for exposing service APIs: HTTP.