Rehashing Orchestration vs Choreography
There is a lot of talk about Sagas and using choreography versus orchestration. I have referenced a few of them below. Having done this a few times with actual implementations, here are some of my thoughts. Let’s start with a customary definition of what sagas are: The saga design pattern is a way to manage data consistency across microservices in a distributed transaction scenario. -microsoft Assuming you have done the pre-work on why microservices are the best approach for your organization, used Domain-Driven Design concepts to identify your subdomains or bounded contexts, and aligned your organization around them, you will end up with a bunch of services within one bounded context (like the colored ones at the start of this post). Now you are trying to ensure that your architecture is loosely coupled, failure-resistant, handles distributed transactions, scales with traffic, etc. ...