Microservices - Orchestration with Kubernetes
You need to design a microservices system where services must communicate reliably even if some services are temporarily down. Which pattern best fits this requirement?
You need to design a microservices system where services must communicate reliably even if some services are temporarily down. Which pattern best fits this requirement?
hard📝 Trade-off Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Identify reliability needs
Reliable communication despite downtime requires asynchronous messaging to decouple services.Step 2: Evaluate other options
Synchronous calls fail if a service is down; direct DB sharing breaks microservices principles; monolith is not microservices.Final Answer:
Asynchronous messaging with message queues -> Option AQuick Check:
Reliable comms with downtime = async messaging [OK]
Quick Trick: Async messaging buffers calls when services are down [OK]
Common Mistakes:
MISTAKES- Choosing sync calls for unreliable services
- Using shared DB breaks microservices
- Confusing monolith with microservices
Master "Orchestration with Kubernetes" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes