Microservices - Advanced Patterns
In a choreography-based microservices system, if Service A emits an event and Service B processes it before emitting another event for Service C, what is the key characteristic of this interaction?
In a choreography-based microservices system, if Service A emits an event and Service B processes it before emitting another event for Service C, what is the key characteristic of this interaction?
medium📝 Conceptual Q4 of 15
Step-by-Step Solution
Solution:
Step 1: Identify choreography traits
Choreography means services react to events independently without central control.Step 2: Analyze options
Services communicate through events without a central coordinator. correctly describes event-driven communication without a coordinator. A central orchestrator manages the sequence of service calls. describes orchestration. Services share a common database to synchronize actions. is unrelated. Service B directly calls Service C after processing. implies direct calls, not event-driven.Final Answer:
A -> Option AQuick Check:
Event-driven, decentralized communication is choreography [OK]
Quick Trick: Choreography means event-driven, no central controller [OK]
Common Mistakes:
- Assuming a central orchestrator exists in choreography
- Confusing direct service calls with event-driven communication
- Thinking shared databases coordinate choreography
Master "Advanced Patterns" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes