Please log in to watch this conference skillscast.
How can you approach end-to-end business processes crossing multiple microservices? A choreography leverages event collaboration, orchestration suggests a request-and-response oriented style. Which pattern should you prefer? In this talk, Martin will explore the arguments put forward for one or the other and challenge them more than is normally done. Martin will share with you that orchestration is neither necessarily more central nor necessarily tighter coupled than choreography. Martin will also try to activate the right side of your brain and consider people and behaviour in organisations. And he will reorient the discussion to what matters to a microservices architecture: independently deployable units! Modeling services around business capabilities requires to relentlessly ask: which unit is responsible for a decision? Approaching the goal from this direction, you see the communication pattern as a local consequence! Expect many examples for how to mix and match orchestration and choreography to maximize team and service autonomy.
YOU MAY ALSO LIKE:
Stop Bashing Orchestration! And Long Live Choreography!
For over a decade Martin has been working in complex domains like energy trading, telecommunication or wind tunnel organization. As a coder, he has had a soft spot for readable and testable APIs and enjoys working with sophisticated but lean state machines and process engines. As a domain coder, he is into Domain-Driven Design and integrates methods which shift his focus from technology to the user value of what he does. Martin is a contributor to several projects on GitHub and speaks at meetups and conferences like ExploreDDD, O'Reilly and KanDDDinsky.