Bird
0
0

Why is the Strangler fig pattern considered a safer approach compared to a big-bang rewrite in microservices migration?

hard📝 Conceptual Q10 of 15
Microservices - Migration from Monolith
Why is the Strangler fig pattern considered a safer approach compared to a big-bang rewrite in microservices migration?
ABecause it requires no testing during migration
BBecause it allows incremental migration and rollback if needed
CBecause it forces immediate client changes
DBecause it replaces the entire system in one step
Step-by-Step Solution
Solution:

  1. Step 1: Compare migration approaches

    Strangler fig migrates incrementally, allowing testing and rollback.

  2. Step 2: Understand risks of big-bang rewrite

    Big-bang replaces all at once, increasing risk and downtime.

  3. Final Answer:

    Because it allows incremental migration and rollback if needed -> Option B

  4. Quick Check:

    Incremental migration = safer = B [OK]
Quick Trick: Incremental migration enables rollback [OK]
Common Mistakes:
  • Thinking no testing is needed
  • Assuming immediate client changes
  • Believing in one-step replacement

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Advanced Patterns - Ambassador pattern - Quiz 2easy Advanced Patterns - Anti-patterns (distributed monolith, chatty services) - Quiz 15hard Advanced Patterns - Sidecar pattern - Quiz 15hard CI/CD for Microservices - Blue-green deployment - Quiz 6medium Configuration and Secrets Management - Why externalized config enables flexibility - Quiz 7medium Configuration and Secrets Management - Config server pattern - Quiz 10hard Migration from Monolith - Incremental migration plan - Quiz 15hard Migration from Monolith - Incremental migration plan - Quiz 9hard Real-World Architecture Case Studies - When to revert to monolith - Quiz 15hard Real-World Architecture Case Studies - When to revert to monolith - Quiz 14medium