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

Hybrid Approaches

Combining orchestration and choreography patterns to balance control with flexibility in practice.

Hybrid Approaches

You'll learn how to combine orchestration and choreography patterns to get the best of both worlds in event-driven systems.

The Core Idea

In practice, complex distributed systems rarely use pure orchestration or pure choreography. Instead, hybrid approaches blend centralized coordination (orchestration) for critical paths with decentralized event handling (choreography) for loose coupling where appropriate.

Think of it like organizing a wedding: you might have a wedding planner (orchestrator) who manages the ceremony timeline and coordinates key moments, while guests (choreographed participants) independently respond to events like "dinner is served" or "dance floor opens" without central control.

How Hybrid Approaches Work

You identify boundaries where each pattern shines:

Use orchestration when:

  • A specific business flow needs explicit visibility and control
  • Failure recovery requires coordinated rollback
  • The sequence is complex and changes frequently

Use choreography when:

  • Services need to react independently to domain events
  • Loose coupling is more valuable than centralized insight
  • Multiple services care about the same event

For example, in an order fulfillment saga:

  • An orchestrator might coordinate the critical path: reserve inventory → charge payment → create shipment
  • Meanwhile, choreographed events notify ancillary services: send confirmation email, update analytics, trigger recommendations

The orchestrator publishes domain events that other services consume independently, giving you visibility where it matters while maintaining flexibility elsewhere.

Finding the Balance

The key is drawing clear boundaries. Services within a bounded context or critical transaction might use orchestration, while cross-context integration relies on choreography. You're not choosing one approach—you're architecting with both intentionally.

Key Takeaway: Hybrid approaches let you apply orchestration for control-critical workflows while using choreography for flexible, decoupled integrations—giving you practical balance over theoretical purity.