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📝 Trade-off Q15 of 15

Microservices - Advanced Patterns

AUse a monolithic architecture to simplify deployment.

BUse orchestration for centralized control and easier debugging.

CUse choreography for loose coupling and better scalability.

DUse shared database coordination for consistency.

Step-by-Step Solution

Solution:

Step 1: Identify scalability and failure requirements
System must scale easily and avoid single failure point, so loose coupling is key.
Step 2: Match pattern to requirements
Choreography allows services to work independently, improving scalability and fault tolerance.
Step 3: Eliminate other options
Orchestration centralizes control, risking single failure point. Monolith and shared DB reduce scalability.
Final Answer:
Use choreography for loose coupling and better scalability. -> Option C
Quick Check:
Loose coupling + scalability = choreography [OK]

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

Common Mistakes:

Master "Advanced Patterns" in Microservices

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Microservices Quizzes