Saga pattern for distributed transactions in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the Saga pattern in microservices?

Consider a system where multiple microservices need to update their data as part of a single business transaction. What is the main goal of using the Saga pattern in this context?

A To coordinate a sequence of local transactions with compensating actions to maintain data consistency without distributed locks.

B To ensure all microservices update their data atomically using distributed locks.

C To replicate data synchronously across all microservices to avoid inconsistencies.

D To use a centralized database to handle all transactions for microservices.

💡 Hint

Think about how Saga handles failures without locking resources across services.

The Saga pattern breaks a distributed transaction into a series of local transactions. Each local transaction updates its service and publishes an event or message. If a step fails, compensating transactions undo the previous steps. This avoids the need for distributed locks or a centralized database.

❓ Architecture

intermediate

Which architecture best represents the Saga pattern with event-based choreography?

In the Saga pattern, event-based choreography means services react to events to continue the transaction. Which diagram best shows this flow?

A All services update a shared database table to track transaction progress.

B A central orchestrator sends commands to each service to perform transactions in order.

C Each service publishes events after completing its local transaction, triggering the next service to act without a central coordinator.

D Services use distributed locks to coordinate transaction steps.

💡 Hint

Think about how services communicate without a central controller in event-based choreography.

In event-based choreography, each service publishes an event after its local transaction. Other services listen for these events and react accordingly. There is no central orchestrator directing the flow.

❓ scaling

advanced

How does the Saga pattern help scale distributed transactions in microservices?

Imagine a high-traffic system with many distributed transactions. How does using the Saga pattern improve scalability compared to traditional two-phase commit?

A By locking all resources globally during the transaction to prevent conflicts.

B By requiring all services to complete their transactions before any service commits.

C By using a single database instance to handle all transaction coordination.

D By breaking transactions into smaller local steps that can run independently and asynchronously, reducing blocking and contention.

💡 Hint

Consider how asynchronous local transactions affect system throughput and resource usage.

The Saga pattern breaks a large distributed transaction into smaller local transactions that run independently and asynchronously. This reduces the need for global locks and blocking, allowing the system to handle more transactions concurrently and scale better.

❓ tradeoff

advanced

What is a key tradeoff when using the Saga pattern for distributed transactions?

While the Saga pattern improves scalability and availability, what is a common tradeoff developers must handle?

A It guarantees strong consistency across all services at all times.

B It requires complex compensating transactions and eventual consistency, which can complicate error handling.

C It eliminates the need for any transaction coordination or monitoring.

D It forces all services to use the same database technology.

💡 Hint

Think about what happens if a step in the Saga fails after some steps have succeeded.

The Saga pattern uses compensating transactions to undo previous steps if a failure occurs. This leads to eventual consistency rather than immediate strong consistency. Designing these compensations and handling partial failures adds complexity.

❓ estimation

expert

Estimate the maximum throughput impact of Saga pattern compensations in a system with 1000 transactions per second and 5% failure rate at step 3.

A Saga consists of 5 steps. Step 3 fails in 5% of transactions, triggering compensations for steps 1 and 2. Each compensation takes 10ms. What is the approximate additional processing time per second due to compensations?

A 1000 transactions * 5% failures * 2 compensations * 10ms = 1000ms (1 second) extra processing per second.

B 1000 transactions * 5% failures * 5 steps * 10ms = 2500ms (2.5 seconds) extra processing per second.

C 1000 transactions * 10ms = 10,000ms (10 seconds) extra processing per second.

D 1000 transactions * 5% failures * 10ms = 500ms (0.5 seconds) extra processing per second.

💡 Hint

Calculate how many compensations run per second and multiply by their duration.

5% of 1000 transactions = 50 failed transactions per second. Each failed transaction triggers 2 compensations, each taking 10ms. Total extra time = 50 * 2 * 10ms = 1000ms = 1 second extra processing per second.