Course contentsShow
← Cloud and Infrastructure
Lesson 2730 of 2,98959. Queueing and Async PatternsFree lesson

Choreography vs Orchestration

Compare choreographed event flows where services react independently versus centrally orchestrated workflows.

Choreography vs Orchestration

What you'll learn: How two fundamental approaches—choreography and orchestration—differ in coordinating distributed async workflows.

The Core Difference

When multiple services need to collaborate in a distributed system, you have two architectural choices for managing the workflow:

Orchestration uses a central coordinator (an orchestrator service) that explicitly tells each participant what to do and when. Think of a conductor leading an orchestra—one leader directs every musician's timing and actions.

Choreography has no central authority. Each service knows its role and reacts to events independently, like dancers who've rehearsed their routine—everyone knows the pattern and responds to each other's moves without a choreographer directing them mid-performance.

When to Use Each

Orchestration works well when:

  • You need clear visibility into workflow state
  • Complex conditional logic determines the sequence
  • Centralized error handling and retry logic is important
  • A single team owns the entire process

Choreography shines when:

  • Services are loosely coupled and autonomously owned
  • The workflow is event-driven and reactive
  • You want to avoid a single point of failure
  • Each team controls their service's behavior independently

The Trade-offs

Orchestration gives you control and visibility but creates coupling to the orchestrator. If it fails, the whole workflow stops. You're also creating a "god service" that knows too much about everyone else.

Choreography distributes intelligence, making the system more resilient and scalable. However, understanding the overall flow requires tracing events across services, and debugging becomes harder when there's no single place showing "what happens next."

Key Takeaway: Orchestration centralizes workflow control for visibility and simplicity; choreography distributes decisions across services for resilience and autonomy—choose based on your coupling tolerance and operational needs.