Strangler Migration
Is this service being extracted from the legacy system safely? One capability at a time, behind a routing layer, with its data, a tested way back and the old code removed.
16 rules · 38% checked automatically
Check your service against it
Apply this checklist to a service described in MICROSERVICE.md™: 6 of its 16 rules are checked against the design automatically, and each failing rule points to where to fix it.
0 of 16 ticked · kept in this browser only
Architecture
- The service names its bounded context
The service says which part of the business it belongs to, so its boundary can be judged and its language is unambiguous.
HighChecked automatically
- One capability is extracted at a time
The migration moves a single business capability end to end, and takes real traffic, before the next one starts.
HighChecked by hand
- A routing layer sits between callers and the service
Requests reach the service through a gateway or proxy that can send each route to the old system or the new one.
HighChecked automatically
- The legacy model stays behind an anti-corruption layer
Calls to and from the legacy system pass through a translation layer, so its data model and quirks don't leak into the new service.
HighChecked by hand
- The data moves with the capability
The extracted service owns the data for its capability in its own store. It does not keep reading or writing the legacy database.
HighChecked by hand
- Calls back to the legacy system are declared
Every call the new service still makes to the legacy system is listed as a dependency, with what it is for and how failure is handled.
MediumChecked by hand
- Behaviour is compared with the legacy system before cutover
The new service is run against real traffic alongside the old one, and the differences are examined, before it serves users.
HighChecked by hand
- The replaced legacy code is removed
Once the new service carries all the traffic, the old code path, its data and its routes are deleted.
MediumChecked by hand
Data
- The service owns its data and says what it holds
Each data store belongs to this service alone, and the design says what is kept in it.
HighChecked automatically
Resilience
- Hard dependencies have a timeout
Every synchronous call the service cannot work without has a declared timeout.
CriticalChecked automatically
API
- The API is covered by contract tests
Tests check that the service still answers the way its consumers expect, and run before every release.
MediumChecked by hand
Deployment
- Traffic moves to the new version in steps
A release, or a cutover, reaches a small share of traffic first and grows only while the metrics stay healthy.
MediumChecked by hand
- Cutover is a routing change, not a release
Switching traffic between the old system and the new service is a configuration change that takes effect in minutes.
HighChecked by hand
- The way back to the legacy system has been rehearsed
The team has switched traffic back to the old system at least once, on purpose, and knows what happens to the data written meanwhile.
HighChecked by hand
Observability
- Alerts are defined
The service has alerts on symptoms its users would notice, each one actionable.
HighChecked automatically
Decisions
- Key decisions are recorded
At least one architecture decision is written down and accepted, with its context and consequences.
LowChecked automatically