Most modern applications are distributed, integrate with third-party services, and expose APIs. Although the cloud, serverless, and automation have made distributed systems management easier, fundamental challenges like latency, throttling, or out-of-order delivery remain. Enterprise Integration Patterns have helped developers design distributed message flows for over two decades, but scalable distributed systems must also tackle operational aspects like flow control, in-order delivery, and retry logic.
Taking the “Fallacies of Distributed Computing” one level up (and inverting towards positive outcomes), attendees learn how queues invert control flow but require flow control, why loose coupling isn’t always the best choice, and why retry logic can take your system down.
Key Takeaways
1 A more nuanced understanding of coupling between distributed systems
2 How to design asynchronous systems that are resilient against failure and perform predictably under high load
3 An intuitive notation to model control flow across distributed systems
4 In-depth discussion with the co-author of the timeless classic 'Enterprise Integration Patterns'
Speaker
Gregor Hohpe
Author of "Enterprise Integration Patterns" and "The Software Architect Elevator", Cloud Architect, Member of IEEE Software Advisory Board, Previously @AWS, @Google, and @Allianz
Gregor helps technology leaders transform both their organization and their technology platform. You’ll find him riding the Architect Elevator from the engine room to the penthouse, perhaps automating serverless solutions in the morning and preparing board presentations in the afternoon. His favorite pastime is dissecting buzzwords and replacing them with meaningful decisions and architectural trade-offs.
Gregor is known as co-author of the seminal book Enterprise Integration Patterns, which provided the reference vocabulary for all modern ESBs. His book The Software Architect Elevator tells stories from the trenches of IT transformation while his articles have been featured in Best Software Writing by Joel Spolsky and 97 Things Every Software Architect Should Know. He is an active member of the IEEE Software advisory board.
intermediate to advanced
