Overview
What this challenge is about.
Stand up an HTTP facade in front of the monolith (Nginx or a small Go proxy) that routes by URL pattern. Slice 1: extract the order-status read endpoint, dual-write nothing, route reads to the new Go service backed by a read replica. Slice 2: extract order cancellation — a low-risk write — with feature-flagged routing per merchant and dual-write to the monolith for reconciliation. Slice 3: extract order creation behind a percentage rollout with explicit rollback. Deliver the running facade + new service, the reconciliation report (zero mismatches required), and the 7-page playbook with rollout, rollback, and observability patterns.
The Brief
What you'll do, and what you'll demonstrate.
Execute the first three slices of a strangler-fig migration from a PHP order monolith to a Go service, with zero downtime and dual-write reconciliation.
Earning criteria — what you'll demonstrate
- Apply the strangler-fig pattern as iterative slices, not a parallel rewrite
- Design dual-write reconciliation that catches divergence before customers do
- Use feature flags + percentage rollouts to bound migration blast radius
- Document a migration playbook reusable across subdomains
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.