Design Microservices Architecture with Patterns and Principles - SAGA Pattern - Choreography-Based SAGA Implementation

The video tutorial explains the choreography-based implementation of the Saga pattern in microservices. It highlights how microservices communicate through events using a message broker, allowing for decentralized and flexible transaction management. An example of this approach is demonstrated in an e-commerce order fulfillment scenario. The video also covers error handling and rollback mechanisms in choreography, along with the benefits and drawbacks of using this approach. Choreography is suitable for simple workflows but can become complex with increased transaction steps.

What is the primary communication method used in choreography-based SAGA implementation?

• Event exchange via message broker

• Centralized orchestrator

• Shared database

• Direct API calls

In the e-commerce example, what triggers the inventory microservice to reserve items?

• A direct request from the customer

• An event from the order microservice

• A scheduled task

• A notification from the payment microservice

How does the choreography-based SAGA handle a failure during the inventory reservation step?

• It retries the transaction automatically

• It ignores the failure and continues

• It publishes a failure event to trigger compensating transactions

• It sends an alert to the system administrator

What is one of the main benefits of using a choreography-based approach?

• Simplified debugging

• Centralized control

• Decentralized and flexible coordination

• Reduced network traffic

Which of the following is a drawback of choreography-based SAGA?

• Increased dependency on a central orchestrator

• Complexity in managing event-based communication

• Limited scalability

• Inability to handle failures

Why might choreography-based SAGA not be suitable for complex workflows?

• It is too costly to implement

• It lacks flexibility

• It becomes confusing with many transaction steps

• It requires too many microservices

What risk is associated with cyclic event consumption in choreography-based SAGA?

• Security vulnerabilities

• Data loss

• Increased latency

• Cyclic dependency issues