Microservices - Migration from Monolith
A team notices that two microservices share the same database schema and tables. What is the main issue here?
A team notices that two microservices share the same database schema and tables. What is the main issue here?
medium📝 Conceptual Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Understand database sharing impact
Sharing the same database schema creates tight coupling between services.Step 2: Evaluate service independence
Services lose independence and cannot evolve or deploy separately.Final Answer:
Tight coupling due to shared database -> Option DQuick Check:
Shared database = A [OK]
Quick Trick: Each service should own its database [OK]
Common Mistakes:
- Thinking shared DB improves independence
- Ignoring coupling from shared schema
- Assuming data consistency justifies sharing
Master "Migration from Monolith" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes