Balancing Choreography and Orchestration

This SkillsCast is currently only available to registered attendees of Software Architecture Gathering Digital 2021

It will be freely available to all Skills Matter members once the Software Architecture Gathering Digital 2021 early-access window expires on January 14, 2022.

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 Course on 8th - 12th November 2021)
• Domain-Driven Design Hands-On Workshop: A DDD-traineeship at "Carries Cars" (Online Meetup on 26th October 2021)
• Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)
• F# Gives You Superpowers (SkillsCast recorded in October 2021)