Comparison of choreography vs orchestration based Saga patterns in microservices

Microservice Architecture (MSA) is a design and architecture pattern created to deal with the challenges of conventional software programs in terms of stream processing, highly available flexibility, and infrastructural agility. Despite the many advantages of MSA, designing isolated services using the autonomous Databases per Services paradigm is difficult. We realized that because each microservice will have its repository, ensuring data coherence between databases becomes difficult, especially in reversals, where operations transcend different sites. Distributed networked transactions and rollbacks can be efficiently handled using two-phase commitment methods in hardware virtualization using RDBMS databases. However, these approaches can't be used in micro-services with segregated NoSQL servers. Three issues have been addressed in this study: (i) investigate the implementation of event choreography and orchestration methods for the Saga pattern execution in MSA, (ii) existing reality suggestions on the saga pattern adoption and implementation besides the use cases, and (iii) introduce the disbursed transaction records and rollbacks challenges in isolated No-SQL databases with reliant collections in MSA.