Course contentsShow
← Software Engineering
Lesson 1377 of 1,93340. Event-Driven ArchitectureFree lesson

When to Use Choreography

Scenarios favoring choreography: loose coupling, scalability, and independent service evolution.

When to Use Choreography

You'll learn when choreography becomes the right choice for orchestrating distributed workflows.

The Core Idea

Choreography shines in scenarios where you want services to operate independently without a central controller. Each service knows its own responsibilities and reacts to events published by others, making the system highly decoupled and naturally scalable.

Think of choreography like a flash mob: each dancer knows the routine and reacts to the music and others' movements, but there's no stage director calling the shots during the performance.

Ideal Use Cases

Loose Coupling Requirements

When services need to evolve independently without coordinating changes through a central authority, choreography allows each service to subscribe to events it cares about and ignore the rest. New services can join the dance without existing ones even knowing.

High Scalability Demands

Because there's no single orchestrator that can become a bottleneck, choreographed systems naturally distribute load. Each service processes events at its own pace, and you can scale consumers independently based on their workload.

Independent Service Evolution

When different teams own different services and need to deploy on their own schedules, choreography's decentralized nature means one team's changes don't require coordinating with a central orchestrator. Services communicate through stable event contracts, not direct dependencies.

Simple, Linear Workflows

Choreography works best when the workflow is straightforward: "When X happens, do Y; when Y completes, do Z." Complex branching logic or conditional paths are harder to reason about without centralized visibility.

Key Takeaway: Use choreography when you prioritize loose coupling, independent scalability, and autonomous service evolution over centralized visibility and control—especially for simpler, event-driven workflows where services naturally react to domain events.