Choreography vs orchestration in Microservices - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the key difference between choreography and orchestration in microservices

Which statement best describes the main difference between choreography and orchestration in microservices architecture?

A Both choreography and orchestration require a central controller to coordinate services.

B Choreography relies on a central controller to manage service interactions, while orchestration lets services communicate directly without a central point.

C Orchestration uses a central controller to manage service interactions, while choreography lets services communicate directly without a central point.

D Choreography and orchestration are identical concepts with different names.

💡 Hint

Think about who controls the flow of communication between services.

Orchestration uses a central controller to direct service interactions, while choreography lets services communicate directly and react to events without a central coordinator.

❓ Architecture

intermediate

Choose the architecture diagram that represents choreography

Which architecture diagram best represents choreography in a microservices system?

A Services emit events and other services listen and react to those events without a central controller.

B A central service sends commands to all other services to perform tasks sequentially.

C A single database manages all service states and interactions.

D All services communicate only through a shared message queue controlled by a central orchestrator.

💡 Hint

Look for decentralized event-driven communication.

Choreography is event-driven and decentralized, where services emit and listen to events without a central controller.

❓ scaling

advanced

Scaling challenges in orchestration vs choreography

Which scaling challenge is more likely to occur in orchestration compared to choreography?

A Services struggle to discover each other due to lack of central coordination.

B The central orchestrator becomes a bottleneck as the number of services grows.

C Event propagation delays increase exponentially with more services.

D Services cannot handle asynchronous communication effectively.

💡 Hint

Consider the role of the central controller in orchestration.

In orchestration, the central controller can become a bottleneck when many services depend on it, limiting scalability.

❓ tradeoff

advanced

Tradeoff between observability in choreography and orchestration

Which statement correctly describes the tradeoff in observability between choreography and orchestration?

A Orchestration provides better observability due to centralized control, while choreography requires distributed tracing.

B Orchestration makes observability harder because services communicate directly without logs.

C Choreography offers easier observability because all interactions are managed centrally.

D Both choreography and orchestration have identical observability challenges.

💡 Hint

Think about where the control and logs are centralized.

Orchestration centralizes control, making it easier to observe workflows, while choreography requires tracing across distributed services.

❓ estimation

expert

Estimate message volume in choreography vs orchestration

In a system with 10 microservices where each service triggers 3 downstream services per request, which approach likely generates more total messages for 1000 requests?

A Neither generates messages because services communicate synchronously.

B Orchestration generates more messages because the central controller sends commands to all services.

C Both generate the same number of messages because the workflow is identical.

D Choreography generates more messages because each service emits events that multiple services listen to independently.

💡 Hint

Consider how events propagate in choreography versus commands in orchestration.

Choreography involves multiple event emissions and listeners, often causing more messages than a central orchestrator sending direct commands.

Practice

1. Which statement best describes choreography in microservices architecture?

easy

A. A central controller manages all service interactions and workflow.

B. Services communicate directly through events without a central controller.

C. Services are tightly coupled and depend on a single database.

D. All services share the same codebase for coordination.

Solution

1. Step 1: Understand choreography communication style

   Choreography means services send and receive events directly without a central manager.

2. Step 2: Compare with orchestration

   Orchestration uses a central controller, unlike choreography which is decentralized.

3. Final Answer:

   Services communicate directly through events without a central controller. -> Option B

4. Quick Check:

   Choreography = direct event communication [OK]

Hint: Choreography means no central boss, services talk directly [OK]

Common Mistakes:

• Confusing choreography with orchestration
• Thinking choreography requires a central controller
• Assuming choreography means tight coupling

2. Which of the following is the correct syntax to describe orchestration in microservices?

easy

A. A central orchestrator calls each service in sequence.

B. Services share a global state without coordination.

C. Services emit events and listen to each other directly.

D. Services communicate only through a shared database.

Solution

1. Step 1: Identify orchestration pattern

   Orchestration uses a central controller that manages service calls in order.

2. Step 2: Eliminate incorrect options

   Options A, B, and D describe other patterns or incorrect behaviors.

3. Final Answer:

   A central orchestrator calls each service in sequence. -> Option A

4. Quick Check:

   Orchestration = central controller calls [OK]

Hint: Orchestration means one boss controls the workflow [OK]

Common Mistakes:

• Mixing event-driven with orchestrated calls
• Assuming orchestration means no central control
• Confusing shared database with orchestration

3. Consider this scenario: Service A emits an event, Service B listens and processes it, then emits another event for Service C. Which pattern is this an example of?

medium

A. Choreography with event-driven communication

B. Orchestration with central controller

C. Monolithic service call chain

D. Shared database coordination

Solution

1. Step 1: Analyze event flow

   Service A emits event, B listens and emits another event, C listens next. This is event-driven chain.

2. Step 2: Match pattern to description

   This direct event passing without central control matches choreography.

3. Final Answer:

   Choreography with event-driven communication -> Option A

4. Quick Check:

   Event chain without central control = Choreography [OK]

Hint: Event chain without boss = choreography [OK]

Common Mistakes:

• Assuming event flow means orchestration
• Confusing monolith with microservices
• Thinking shared database is event-driven

4. A developer implemented orchestration but forgot to handle failures in the central controller. What is the likely problem?

medium

A. Services will communicate directly causing chaos.

B. There will be no impact since orchestration is event-driven.

C. Services will ignore the central controller and run independently.

D. The workflow may stop or behave unpredictably on errors.

Solution

1. Step 1: Understand orchestration failure impact

   Central controller manages workflow; missing error handling causes stops or bad states.

2. Step 2: Eliminate wrong options

   Options A and C describe choreography or independent services, not orchestration failure. There will be no impact since orchestration is event-driven. is false because orchestration is not event-driven.

3. Final Answer:

   The workflow may stop or behave unpredictably on errors. -> Option D

4. Quick Check:

   Orchestration needs error handling to avoid workflow breaks [OK]

Hint: No error handling in orchestrator breaks workflow [OK]

Common Mistakes:

• Confusing orchestration failure with choreography behavior
• Ignoring error handling importance
• Assuming orchestration is event-driven

5. You need to design a microservices system that must scale easily and avoid a single point of failure. Which approach is better and why?

hard

A. Use a monolithic architecture to simplify deployment.

B. Use orchestration for centralized control and easier debugging.

C. Use choreography for loose coupling and better scalability.

D. Use shared database coordination for consistency.

Solution

1. Step 1: Identify scalability and failure requirements

   System must scale easily and avoid single failure point, so loose coupling is key.

2. Step 2: Match pattern to requirements

   Choreography allows services to work independently, improving scalability and fault tolerance.

3. Step 3: Eliminate other options

   Orchestration centralizes control, risking single failure point. Monolith and shared DB reduce scalability.

4. Final Answer:

   Use choreography for loose coupling and better scalability. -> Option C

5. Quick Check:

   Loose coupling + scalability = choreography [OK]

Hint: Loose coupling means choreography for scale and fault tolerance [OK]

Common Mistakes:

• Choosing orchestration despite single failure risk
• Confusing monolith with microservices
• Ignoring scalability in design choice