You design a microservice that calls a payment gateway. To avoid delays, you want to use the fallback pattern. Which fallback strategy is best to keep the system responsive and safe?

hard📝 Trade-off Q15 of 15

Microservices - Resilience Patterns

AReturn a generic error message without fallback

BReturn a cached success response immediately and update later asynchronously

CRetry the payment gateway call 10 times before fallback

DRestart the payment microservice on failure

Step-by-Step Solution

Solution:

Step 1: Understand fallback goals for payment service
Fallback should keep system responsive and avoid blocking user with delays.
Step 2: Evaluate options for responsiveness and safety
Returning cached success immediately and updating asynchronously balances responsiveness and eventual consistency.
Step 3: Eliminate risky or slow options
Retries cause delays, generic errors hurt UX, restarting service is costly and slow.
Final Answer:
Return a cached success response immediately and update later asynchronously -> Option B
Quick Check:
Cached immediate fallback with async update = best practice [OK]

Quick Trick: Use cached immediate fallback plus async update [OK]

Common Mistakes:

MISTAKES

Excessive retries causing delays
No fallback causing poor user experience
Restarting services on failure

Master "Resilience Patterns" 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

You design a microservice that calls a payment gateway. To avoid delays, you want to use the fallback pattern. Which fallback strategy is best to keep the system responsive and safe?

Step 1: Understand fallback goals for payment service

Step 2: Evaluate options for responsiveness and safety

Step 3: Eliminate risky or slow options

Final Answer:

Quick Check:

Want More Practice?