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

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the Saga pattern in distributed systems?

Choose the best explanation for why the Saga pattern is used in distributed transactions.

A To replicate data synchronously across all services to avoid inconsistencies.

B To lock all resources across microservices until the entire transaction completes to ensure atomicity.

C To coordinate a sequence of local transactions with compensating actions to maintain data consistency without locking resources.

D To batch all operations into a single monolithic transaction for performance.

💡 Hint

Think about how distributed systems avoid long locks and still keep data consistent.

The Saga pattern breaks a distributed transaction into smaller local transactions with compensating actions. This avoids locking resources across services and helps maintain eventual consistency.

❓ Architecture

intermediate

Which Kafka component is best suited to implement the Saga pattern's event coordination?

Select the Kafka component that helps orchestrate and communicate the sequence of events in a Saga.

A Kafka Connect to synchronize databases directly without event handling.

B Kafka Schema Registry to store transaction logs.

C Kafka Streams to batch process unrelated data without event ordering.

D Kafka Topics to publish and subscribe to events representing transaction steps and compensations.

💡 Hint

Think about how services communicate asynchronously in a Saga.

Kafka Topics are used to publish events for each transaction step and compensating action, enabling services to react and coordinate asynchronously.

❓ scaling

advanced

How does the Saga pattern scale when handling thousands of distributed transactions concurrently?

Choose the best explanation of how Saga pattern scales in a Kafka-based microservices environment.

A By replicating the entire Saga state machine on every microservice instance to avoid coordination.

B By partitioning Kafka topics and processing events in parallel, allowing independent Sagas to run concurrently without interference.

C By batching all transactions into one large event to reduce overhead.

D By serializing all transactions through a single Kafka partition to maintain strict order.

💡 Hint

Consider how Kafka partitions help parallelize event processing.

Kafka partitions allow events for different Sagas to be processed independently and in parallel, enabling high throughput and scalability.

❓ tradeoff

advanced

What is a key tradeoff when using the Saga pattern compared to traditional two-phase commit (2PC)?

Select the option that best describes a tradeoff of Saga pattern usage.

A Saga provides eventual consistency but sacrifices immediate atomicity and may require compensating transactions.

B Saga guarantees immediate atomicity but requires locking all resources during the transaction.

C Saga eliminates the need for compensating transactions by using distributed locks.

D Saga reduces network overhead by batching all operations synchronously.

💡 Hint

Think about consistency guarantees and how compensations work.

Saga sacrifices immediate atomicity for eventual consistency and uses compensating transactions to undo partial work if needed.

❓ estimation

expert

Estimate the maximum throughput of a Saga-based system using Kafka with 10 partitions, each processing 1000 events per second, assuming each Saga requires 5 events.

Calculate the maximum number of Saga transactions the system can handle per second.

A 2000 Saga transactions per second

B 5000 Saga transactions per second

C 500 Saga transactions per second

D 10000 Saga transactions per second

💡 Hint

Divide total event processing capacity by events per Saga.

Total event capacity = 10 partitions * 1000 events/sec = 10,000 events/sec.
Each Saga requires 5 events.
Maximum Saga throughput = 10,000 / 5 = 2000 Sagas/sec.