Balancing Choreography and Orchestration

Please log in to watch this conference skillscast.

These days, many teams favor loose coupling, isolation and autonomy of services and therefore typically opt for event-driven and reactive architectures, using a communication pattern known as choreography. While choreography is beneficial in some situations, it is far from the holy grail of integration. In some scenarios, it increases coupling, often accidentally and to a dangerous degree. Orchestration is a better choice for some situations, but is often bashed for introducing tight coupling. I will debunk some of these myths and show how orchestration can even reduce coupling in some situations and totally work in an asynchronous, message-driven fashion.

TLDR: Choreography vs. orchestration is NOT about choosing THE right approach. In real life, you need to balance both, so it is about choosing wisely on a case-by-case basis. In order to help you with that, I will walk you through the differences and give you some concrete guidance on decision criteria, backed by examples collected in various real-life projects.

YOU MAY ALSO LIKE:

• Process Automation in Cloud-Native Architectures (SkillsCast recorded in December 2020)
• Domain Models in Practice with Marco Heimeshoff (Online Workshop on 6th - 10th June 2022)
• Domain-Driven Design in Practice with Michael Plöd (Online Workshop on 20th - 22nd September 2022)
• Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
• Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)