Microservices - Resilience Patterns
How can you design a health check pattern that avoids false negatives when a dependent service is temporarily slow?
How can you design a health check pattern that avoids false negatives when a dependent service is temporarily slow?
hard📝 Trade-off Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Understand false negatives in health checks
Temporary slowness can cause incorrect unhealthy status if no retries are done.Step 2: Implement timeout and retry
Retrying before marking unhealthy reduces false negatives due to transient issues.Final Answer:
Use a timeout and retry logic before marking unhealthy -> Option BQuick Check:
Retries prevent false negatives in health checks [OK]
Quick Trick: Retry before failing health check to avoid false negatives [OK]
Common Mistakes:
MISTAKES- Failing immediately on first failure
- Ignoring dependency status
- Using wrong HTTP status codes
Master "Resilience Patterns" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes