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

Data

Resilience

API

Deployment

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