Microservices - Migration from Monolith
In a Strangler fig pattern migration, how should traffic be managed between the legacy system and new microservices?
In a Strangler fig pattern migration, how should traffic be managed between the legacy system and new microservices?
easy📝 Conceptual Q3 of 15
Step-by-Step Solution
Solution:
Step 1: Identify migrated features
Determine which features have been moved to new microservices.Step 2: Route requests accordingly
Direct requests for migrated features to new services, others remain on legacy.Final Answer:
Route requests for migrated features to new microservices and others to the legacy system -> Option BQuick Check:
Correct routing ensures smooth migration without service disruption [OK]
Quick Trick: Route only migrated features to new services [OK]
Common Mistakes:
- Routing all traffic to new services prematurely
- Randomly distributing requests causing inconsistency
- Ignoring feature readiness in routing decisions
Master "Migration from Monolith" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes