Choreography vs orchestration By David Boyne

EDA visuals and the book is free thanks to our sponsors:

Manage, secure, and govern every API in your organization.

Delivering Apache Kafka professional services to your business.

Choreography

Using events to talk between services (also bounded contexts). Services interact independently. Event-driven approach.

Example of services that can help with choreography are Amazon SQS, Amazon SNS or Amazon EventBridge.

Orchestration

Flow of state that is normally controlled by the orchestrator. Think of flow chart or state machines. Might consider using orchestration within a bounded context. Normally follows request/response.

Example would be AWS Step Functions.

Extra Resources

Choreography vs Orhestration in the land of Serverless - Great blog on choreography and orchestration through a serverless lense.

Explore other visuals

Inside event-driven architectures

What patterns do we commonly see in event-driven applications?

Local cache copy vs requesting data

Bite sized visual to help you understand local cache vs requests with event-driven architecture.

Producer and consumer responsibilities

What are the responsibilities for our consumers and producers?

Want to work together?

If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.

EDA Visuals: The book

Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer.

This book contains all the visuals in one book, you can download, read offline and explore.

Purchase book $15.00

Purchasing the book supports my work, but for whatever reason if the book is beyond your budget, you can download it for free here.

Purchase book $15.00