A team implemented parallel running but noticed that the new service never receives any requests. What is the most likely cause?

medium📝 Analysis Q14 of 15

Microservices - Migration from Monolith

AThe new service crashed immediately after deployment

BThe routing logic is only sending requests to the old service

CThe old service is not logging requests

DThe new service is slower than the old one

Step-by-Step Solution

Solution:

Step 1: Analyze routing in parallel running
For parallel running, requests must be routed to both old and new services simultaneously.
Step 2: Identify why new service gets no requests
If new service never receives requests, routing likely sends all traffic only to old service.
Final Answer:
The routing logic is only sending requests to the old service -> Option B
Quick Check:
No requests to new service = routing issue [OK]

Quick Trick: Check routing logic if new service gets no requests [OK]

Common Mistakes:

Master "Migration from Monolith" in Microservices

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Microservices Quizzes