A microservices system experiences cascading failures due to synchronous calls and no timeouts. How can redesigning the call pattern improve resilience?

hard📝 Trade-off Q8 of 15

Microservices - Real-World Architecture Case Studies

ARemove retries and rely on manual restarts

BIncrease synchronous call timeout values

CSwitch to asynchronous calls with timeouts and retries

DUse a single database for all services

Step-by-Step Solution

Solution:

Step 1: Identify problem with synchronous calls and no timeouts
Synchronous calls block and propagate failures; no timeouts cause long waits.
Step 2: Apply redesign for resilience
Asynchronous calls decouple services; timeouts and retries handle failures gracefully.
Final Answer:
Switch to asynchronous calls with timeouts and retries -> Option C
Quick Check:
Resilience improvement = Async calls + timeouts [OK]

Quick Trick: Use async calls with timeouts to avoid cascading failures [OK]

Common Mistakes:

Increasing timeout prolongs failure impact
Removing retries reduces fault tolerance
Using single database increases coupling

Master "Real-World Architecture Case Studies" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Microservices Quizzes

A microservices system experiences cascading failures due to synchronous calls and no timeouts. How can redesigning the call pattern improve resilience?

Step 1: Identify problem with synchronous calls and no timeouts

Step 2: Apply redesign for resilience

Final Answer:

Quick Check:

Want More Practice?