Saga choreography vs saga orchestration
Inspired by 50 shades of system design
Saga choreography saga orchestrationin the trade-off explorer →
Either each service triggers the next one, or there is an orchestrator managing the whole thing.
Queen was an orchestrator whereas in PIMS, it was choreography style, retriever triggers transformer, etc.
Sources
- 50 shades of system design inspired this note
Referenced by
- Common System Design PatternsGrowing
Database Replication and read replicas. Something something geolocalisation. Postgres has extensions for this.