Microservices - Migration from Monolith
A microservices team decomposed their database vertically but notices frequent cross-service joins causing latency. What is the likely cause and fix?
A microservices team decomposed their database vertically but notices frequent cross-service joins causing latency. What is the likely cause and fix?
medium📝 Analysis Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Identify problem with vertical decomposition
Vertical decomposition splits by tables/domains, but if services need to join data often, it causes latency.Step 2: Recommend fix
Redesign to reduce cross-service joins by better domain boundaries or data duplication to avoid latency.Final Answer:
Poor vertical decomposition causing cross-service joins; Fix: Redesign to reduce cross-service dependencies -> Option CQuick Check:
Cross-service joins cause latency; fix by better decomposition [OK]
Quick Trick: Cross-service joins mean bad vertical split; redesign domains [OK]
Common Mistakes:
- Confusing horizontal with vertical decomposition issues
- Thinking merging databases fixes latency
- Blaming database type instead of design
Master "Migration from Monolith" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes