Microservices - Resilience Patterns
You need to implement a comprehensive health check for a microservice that depends on a database, a cache, and an external API. Which design best ensures accurate status reporting without causing delays?
Which design best ensures accurate status reporting without causing delays?
hard📝 Trade-off Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand requirements
The health check must verify multiple dependencies accurately without delays.Step 2: Evaluate options
Perform parallel asynchronous checks for all dependencies and aggregate results with timeouts. uses parallel asynchronous checks with timeouts, minimizing latency and providing comprehensive status.Step 3: Identify drawbacks of other options
Check dependencies sequentially and return the first failure immediately. is slower due to sequential checks; Only check the microservice's own status and ignore dependencies to keep it fast. ignores dependencies; Run health checks once daily and cache the result for all requests. is outdated and may mislead.Final Answer:
Perform parallel asynchronous checks for all dependencies and aggregate results with timeouts. -> Option BQuick Check:
Parallel async checks reduce latency and improve accuracy [OK]
Quick Trick: Use parallel async checks with timeouts [OK]
Common Mistakes:
MISTAKES- Checking dependencies sequentially causing slow responses
- Ignoring dependencies in health checks
- Caching health results too long causing stale info
Master "Resilience Patterns" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes