Microservices - Advanced Patterns
Consider a microservice with a Sidecar that handles logging. If the main service crashes, what happens to the Sidecar?
Consider a microservice with a Sidecar that handles logging. If the main service crashes, what happens to the Sidecar?
medium📝 Conceptual Q13 of 15
Step-by-Step Solution
Solution:
Step 1: Understand Sidecar lifecycle dependency
The Sidecar runs in the same environment and shares lifecycle with the main service, so if the main service stops, the Sidecar usually stops too.Step 2: Evaluate other options
Sidecar does not run independently, restart the main service, or switch to backup automatically.Final Answer:
The Sidecar also stops because it shares the same lifecycle -> Option AQuick Check:
Sidecar lifecycle tied to main service = D [OK]
Quick Trick: Sidecar shares lifecycle with main service, stops if service crashes [OK]
Common Mistakes:
- Thinking Sidecar runs independently after crash
- Assuming Sidecar restarts main service
- Believing Sidecar switches to backup automatically
Master "Advanced Patterns" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes