When designing a multi-step order processing Saga using Kafka, which strategy best supports scalability and fault tolerance?

hard📝 Application Q8 of 15

Kafka - Event-Driven Architecture

AImplement a centralized coordinator service that synchronously calls each step's API

BDecouple each step into independent microservices communicating via Kafka topics with event-driven orchestration

CUse a single Kafka topic for all steps and process events sequentially in one service

DStore all Saga state in a relational database and avoid Kafka for communication

Step-by-Step Solution

Solution:

Step 1: Understand scalability and fault tolerance needs
Decoupling steps allows independent scaling and failure isolation.
Step 2: Use event-driven orchestration
Kafka topics enable asynchronous communication and resilience.
Final Answer:
Decouple each step into independent microservices communicating via Kafka topics with event-driven orchestration -> Option B
Quick Check:
Event-driven decoupling supports scalability and fault tolerance [OK]

Quick Trick: Decouple steps with event-driven Kafka orchestration [OK]

Common Mistakes:

Master "Event-Driven Architecture" in Kafka

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kafka Quizzes