Event-driven systems are loosely coupled, easy to maintain, and most importantly, easy to change. They form the core of many microservice architectures but are a great way to build any application, even in a monolith, that needs to welcome change.

Event-driven systems talk to each other asynchronously, blindly broadcasting notifications into a service cloud. Those notifications are handled by whatever client services are interested. These systems eliminate many of the problems associated with orchestrated systems (which work more like synchronous function calls) and are typically much faster than orchestrated systems, but they have their own idiosyncrasies and implementation challenges. This practically-focused session explores the inherent problems in orchestrated systems, and then looks at how choreography can solve those problems. Three approaches to choreography: http-based, pub/sub messaging based, and brokerless swarming systems. We’ll introduce appropriate messaging architectures and frameworks and look at several practical examples.

Finally, we'll look at Event Storming: one of the best approaches to designing choreographed systems. You'll come away from this session understanding both why you should be using choreography for most high-level APIs and how to design and build these systems.\"