The Scenario
Your company has a massive 10-year-old Ruby on Rails monolith. The `Billing` module is slowing down the entire app. Management wants to extract `Billing` into its own Go microservice without taking the site offline.
The Brief
Design a migration plan using the Strangler Fig pattern. Explain how you will route traffic, migrate the database safely, and handle the transition period where both systems must remain in sync.
Deliverables
- An architectural diagram showing the routing layer (API Gateway) intercepting traffic
- A step-by-step phased migration plan (Dark launch, Shadow traffic, Cut-over)
- A strategy for untangling the shared database (dual writes vs. eventual consistency)
Submission Guidance
The hardest part of microservice extraction is the data layer. You cannot just cut a table out of a shared database overnight. Focus on the database synchronization strategy.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.