Richard Birksteiner, CTO


Controlled development

of complex environments with APIs


Controlled development of complex environments with APIs

 If a decision has been made for cloud-native and (therefore) using CI/CD pipelines, opting also for API first is advisable. Cloud-native, CI/CD and API-first act as a kind of trinity. Cloud-native determines what you build on, CI/CD how you make new functionality available, and API-driven integrations ensure that your digital business fits together seamlessly. APIs enable the transition to microservices. These are similar building blocks within development: microservices are more about the 'how' of development, while APIs are more about the 'what', which means that you are already quite close to business processes. Which specific API style you choose is up to you.  In terms of what an API does, it doesn't really matter if it is REST, gRPC or Graph, for example.

Focus and overview

The API is first and foremost an interface for people. It meets the needs of developers, because of, among other things, the simple way of documenting. It also ensures a clear focus on one specific goal, not twenty goals at a time. In addition, APIs provoke design thinking and thus result in a good design that seamlessly matches the objective the customers want to achieve with it. The user is taken as the starting point when building applications. You build, block by block, towards a certain synthesis in the design. Because services are explicitly disconnected, the overview is maintained, even in complex environments.

This is clearly different from traditional systems thinking, in which a lot of analysis has to be done after a monolith has been built. Analysis paralysis can occur in such situations: the developer is no longer clear as to what exactly needs to be done. This negatively impacts how and when the customer can finally get started.

Futureproof development

When building a new application environment, it is important that it can last for a longer period of time, regardless of changing needs. APIs allow for this, even for wishes that have yet to be imagined by the customer. Regarding internal or external links to applications, for example.

APIs are highly suitable for making a relatively easy connection with things in the outside world, such as applications of and at third parties, since it is easy to find out what a certain API does and why it exists. These are important conditions for opening it up to third parties. Concerning APIs we can again be clear: All our choices in the field of the development environment are based on our desire for scalability and continuous innovation.

Do you want to know more about Richard?

Do you want to get started with the cloud native within your organization after reading this blog or whitepaper? Or do you have questions about the discussed topics? Then contact us:

Richard Birksteiner
+31 (0)299 200 800