Microservices - Real-World Architecture Case Studies
A team claims their microservices system is at maturity level 4 but they still deploy services manually and have no automated rollback. What is the main issue here?
A team claims their microservices system is at maturity level 4 but they still deploy services manually and have no automated rollback. What is the main issue here?
medium📝 Analysis Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Understand level 4 requirements
Level 4 focuses on automation, continuous integration, and continuous delivery including automated rollback.Step 2: Identify missing features in the claim
Manual deployment and no rollback means automation is missing, which contradicts level 4 maturity.Final Answer:
They are missing automation and continuous delivery features -> Option BQuick Check:
Level 4 = Automation & CI/CD [OK]
Quick Trick: Level 4 requires automation; manual deploy means not level 4 [OK]
Common Mistakes:
- Confusing service discovery with automation
- Thinking independent services imply automation
- Ignoring rollback as part of automation
Master "Real-World Architecture Case Studies" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes