You plan to migrate a monolith to microservices incrementally. Which approach best ensures minimal downtime and rollback capability?

hard📝 Trade-off Q15 of 15

Microservices - Migration from Monolith

ADeploy new microservices behind a feature flag and route a small % of traffic gradually

BReplace the monolith entirely in one deployment window

CMigrate database schema all at once without backward compatibility

DDisable old services immediately after deploying new ones

Step-by-Step Solution

Solution:

Step 1: Evaluate migration strategies
Deploying behind feature flags and routing small traffic allows gradual testing and rollback.
Step 2: Compare risks of other options
Replacing all at once or disabling old services causes downtime; schema changes without compatibility break systems.
Final Answer:
Deploy new microservices behind a feature flag and route a small % of traffic gradually -> Option A
Quick Check:
Feature flags + gradual traffic = safe migration [OK]

Quick Trick: Use feature flags and gradual traffic shift for safety [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