Explore the intricacies of balancing choreography and orchestration in software architecture through this insightful conference talk by Bernd Rücker at GOTO 2020. Delve into the advantages and drawbacks of event-driven architectures, examining scenarios where choreography may inadvertently increase coupling. Learn how orchestration can sometimes reduce coupling and operate in an asynchronous, message-driven manner. Discover practical examples of synchronous and asynchronous call chains, peer-to-peer event chains, and stateful orchestration. Gain valuable insights on deciding responsibilities, using workflow engines, and addressing challenges related to commands versus events. Enhance your understanding of modern IT architecture and make informed decisions about integrating choreography and orchestration in your software design.
Overview
Syllabus
Intro
Orchestration vs choreography
Example
Synchronous call chains
Asynchronous call chains
Choreography or orchestration?
Event-driven
P2P event chains
Decide about responsibility
Stateful orchestration
Glue code e.g. Java
Using a workflow engine
Challenge: Command vs event
Your IT architecture
Summary
Taught by
GOTO Conferences
