Do APIs Really Eat All the Pies? Integration Patterns and Their Trade-Offs

Dirk Fröhner
Dirk Fröhner Amazon Web Services
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.

Smarter Tech Decisions Using APIs

Smarter Tech Decisions Using APIs

API blog

High impact blog posts and eBooks on API business models, and tech advice

API conferences

Connect with market leading platform creators at our events

API community

Join a helpful community of API practitioners

API Insights Straight to Your Inbox!

Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.

Join Our Thriving Community

Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.