Knowledge for integration architects

Practical knowledge for integration architects

In-depth articles, expert streams, and real-world insights on integration architecture, patterns, and technologies.

Browse latest articles

Explore topics

View all topics →

Latest knowledge

View all content →

The business value of Application Integration

Have you seen or read “The Twelve Tasks of Asterix”? Do you recall "The Place That Sends You Mad" task? While this is most of all a joke on bureaucracy, you can also think of it as living in an environment without communication. Regardless of the mechanics behind – paper documents delivered to the offices by internal messenger, pneumatic tubes system, modern computer network, Telepathy data transfer – the problem is that data is not flowing from one involved party (office) to the other. As a result, no work is being done and finally the system collapses when disturbance is introduced (it is the purposeful action of Asterix in the movie/comic… but could be anything in the real world).

Hubert DrabczykApr 3, 2026

API-Led One-way point-to-point

As we dive deeper into API-Led Architecture, we can notice that some patterns resemble those found in a different Ecosystem Architectural Style - specifically Event-Driven Architecture (EDA). This similarity exists because API-Led Architecture inherits qualities, so also patterns, from EDA. As API-Led introduces new capabilities, it also addresses challenges that were difficult or impossible to solve in the architectural styles it draws from. In this article, we will discuss the key differences that API-Led Architecture brings to the one-way point-to-point pattern.

Karol SkrzymowskiAug 27, 2025

[TO BE RESCHEDULED!] Loosely Coupled - APIs - moving beyond specification and documentation to actionable knowledge

In today's distributed IT world APIs are everywhere! We use them to send statuses, query data, post social-media posts, and most of all we use them in systems in our organizations. But do we really understand the landscapes they create? In today's distributed IT world APIs are everywhere! We use them to send statuses, query data, post social-media posts, and most of all we use them in systems in our organizations. But do we really understand the landscapes they create? Let’s discuss why an API catalog is only a starting point! How can OpenAPI and AsyncAPI contracts, quality checks, enterprise architecture, ownership, and runtime relationships be connected? Can we digest this knowledge and derive more meaning out of it? Joining us this session is Daniel Kocot, Principal Integration Architect @ adorsys, and together we will take a look at what a graph-based knowledge layer makes possible. Can we, using the API Knowledge Stack as a practical example, follow the path from an API definition and a quality finding to an actionable view of the API, its context, its responsibilities, and its next steps. We’ll be also looking beyond discovery: how APIs can become curated API products, how teams can preserve the intended use and trust, and how organizations can keep their knowledge useful without turning governance into bloated bureaucracy. How do we move from knowing where an API is to understanding what it means and what to do with it? Join us in the discussion!

Daniel KocotOct 7, 2026

Vendor-neutral. Architect-focused. Community-driven.BridgingTheGap.eu.com in Enterprise Application Integration.

Learn more about us →