PICK OUR BRAINS ON A WIDE RANGE OF INTEGRATION TOPICS

In the dynamic world of IT, there inevitably comes a tipping point where ad-hoc solutions no longer suffice. Such solutions typically arise from ad-hoc architectures. However, as businesses grow and technology evolves, the need for a structured approach becomes undeniable. Eventually, ad-hoc architecture loses its effectiveness.

What are good usages for unified APIs?
We expect to see them more and more assisting you in decreasing your time to market.

This article explores a dual approach to implementing a public API strategy that blends the business and technological aspects of API products.

In this blog, we will explore the observability concept, why it is a worthwhile investment for modern businesses, and how to implement it effectively. Let’s start with establishing a clear understanding of the concept of observability and the Observability Maturity Model.

Much has already been discussed about orchestration vs. choreography. The topic tends to divide the best of friends into either the orchestration camp or the choreography camp.

When working with an Event Driven architecture, addressing this topic is essential since EDA is fundamentally needed when building a system that uses the concept of choreography.

“In my previous blog, I delved deeper into the meaning of Event-Driven Architecture. This blog marks the second part of a series dedicated to exploring Event-Driven Architecture. It is important to note that the viewpoints expressed in these blogs are my own and are subject to ongoing discussions within our community”. Our Integration Architect Joost sets the scene!