Saga pattern for distributed transactions in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Saga pattern in distributed transactions?

The Saga pattern breaks a large transaction into smaller steps, each with its own local transaction and compensating action. It ensures data consistency across services without locking resources for a long time.

intermediate

How does RabbitMQ help implement the Saga pattern?

RabbitMQ acts as a message broker to send and receive events between services. It helps coordinate the steps of the Saga by passing commands and compensations reliably and asynchronously.

beginner

What is a compensating transaction in the Saga pattern?

A compensating transaction is an action that reverses the effect of a previous step if something fails later. It helps maintain consistency by undoing partial changes.

intermediate

What are the two main types of Saga execution styles?

1. Choreography: Services communicate by emitting and listening to events without a central coordinator.<br>2. Orchestration: A central orchestrator sends commands to services to perform steps and handle compensations.

intermediate

Why is the Saga pattern preferred over distributed two-phase commit in microservices?

Saga avoids locking resources for long periods, improving system availability and scalability. It fits better with asynchronous, loosely coupled microservices architectures.

What role does RabbitMQ play in the Saga pattern?

A Message broker to coordinate steps asynchronously

B Database to store all transaction data

C Load balancer for microservices

D Cache for fast data retrieval

RabbitMQ is used as a message broker to send and receive messages that coordinate the Saga steps asynchronously.

What happens if a step in a Saga fails?

A The entire system shuts down

B Compensating transactions undo previous steps

C The transaction commits anyway

D The service retries infinitely without rollback

Compensating transactions are triggered to undo previous successful steps to maintain consistency.

Which Saga execution style uses a central coordinator?

A Two-phase commit

B Choreography

C Orchestration

D Event sourcing

Orchestration uses a central orchestrator to send commands and manage the Saga flow.

Why is Saga pattern better for microservices than two-phase commit?

A It locks resources longer

B It is synchronous and blocking

C It requires a central database

D It improves availability and scalability

Saga avoids long locks and blocking, making microservices more available and scalable.

In Saga, what is the purpose of a compensating transaction?

A To reverse a previous step if needed

B To commit the transaction

C To speed up the transaction

D To log the transaction

Compensating transactions undo previous steps to keep data consistent if a later step fails.

Explain how the Saga pattern manages distributed transactions using RabbitMQ.

Think about how messages flow between services to keep data consistent.

Describe the difference between Saga choreography and orchestration styles.

Consider who controls the flow of the Saga in each style.