Microservices - Resilience Patterns
You design a microservice system where the payment service may fail. To apply graceful degradation, which approach is best?
You design a microservice system where the payment service may fail. To apply graceful degradation, which approach is best?
hard📝 Trade-off Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand graceful degradation for critical service failure
When payment service fails, system should still respond with limited info, not block or error out.Step 2: Evaluate options for best graceful degradation
Return a simplified confirmation without payment details and log failure for retry returns simplified confirmation and logs failure for retry, maintaining user experience and system reliability.Final Answer:
Return a simplified confirmation without payment details and log failure for retry -> Option AQuick Check:
Simplified response + retry = graceful degradation [OK]
Quick Trick: Simplify response and log failure for retry [OK]
Common Mistakes:
MISTAKES- Blocking entire process on failure
- Sending immediate error without fallback
- Removing critical service entirely
Master "Resilience Patterns" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes