Modern applications rarely live in isolation, and are themselves typically composed of loosely-coupled components. Such applications must address the fundamental challenges of distributed systems, including out-of-order delivery, idempotence, or partial failures.

Working on the integration architecture in this context, architects need to consider common design trade-offs for distributed systems, and how to navigate them with integration and conversation patterns. Following an API-first strategy is straight-forward, but can be limiting: Looking for a way to communicate between systems, publish events, call third-party services, or externalize states, additional integration approaches, such as messaging, are at our disposal and can even make our

applications more reliable and resilient & allow for offloading responsibility and code.

In this session, learn how established design patterns, such as enterprise integration patterns, help with designing distributed systems. And, based on example scenarios, when you should think about going beyond APIs to make your integration architecture as loosely coupled as your flexibility, scalability, and system evolution goals require.