[Solved] Consider this simplified request flow in a Strangler fig pattern: Legacy system handles requests for features A, B, C.... What happens when a request for feature B arrives? | Microservices

Microservices - Migration from Monolith

Consider this simplified request flow in a Strangler fig pattern:

Legacy system handles requests for features A, B, C.
New microservice replaces feature A.
Requests for A go to new service; B and C go to legacy.
What happens when a request for feature B arrives?

AIt is routed to the new microservice handling feature A

BIt is routed to the legacy system since B is not replaced yet

CIt causes an error because feature B is missing in new service

DIt is dropped and not processed

Step-by-Step Solution

Solution:

Step 1: Analyze routing rules for features
Only feature A is replaced by the new microservice; B and C remain in legacy.
Step 2: Determine routing for feature B request
Requests for B still go to legacy system as it is not replaced yet.
Final Answer:
It is routed to the legacy system since B is not replaced yet -> Option B
Quick Check:
Feature B not replaced = legacy route = C [OK]

Quick Trick: Unreplaced features stay on legacy system [OK]

Common Mistakes:

Routing all requests to new service regardless of feature
Assuming missing features cause errors
Dropping requests instead of routing properly

Master "Migration from Monolith" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

More Microservices Quizzes

Consider this simplified request flow in a Strangler fig pattern:

Step 1: Analyze routing rules for features

Step 2: Determine routing for feature B request

Final Answer:

Quick Check:

Want More Practice?