Strangler-fig migration from a monolith template

Components in this architecture diagram

• Users
• Routing facade
• Route migrated?
• Legacy monolith
• New services
• Legacy database
• Customer service
• Billing service
• Customer DB
• Billing DB
• Change data capture
• Sync to new stores
• Anti-corruption layer
• Shadow traffic comparison

How to use this architecture diagram template

1. Click Open in the editor. The architecture diagram opens on a new page in FlowDiagram — nothing is uploaded and there is no sign-up.
2. Rename, add or delete shapes and drag them where you want; connectors stay attached as things move.
3. Drop in vendor logos from the library — 1,160 of them, including every AWS, Azure and Google Cloud service icon — or restyle it with the colour and theme controls.
4. Prefer text? Edit the Mermaid source below and paste it in through ☰ → Import diagram (see the Mermaid editor); it imports as an editable diagram.
5. Export to PNG, SVG or PDF, or press Ctrl+L for a link that carries the whole diagram.

Mermaid source

The whole template is the text below. Paste it into FlowDiagram, keep it in Git next to the code it describes, or hand it to an AI assistant to extend.

flowchart LR
  U((Users)) --> PROXY[Routing facade]
  PROXY --> R{Route migrated?}
  R -->|No| MONO[Legacy monolith]
  R -->|Yes| NEW[New services]
  MONO --> LDB[(Legacy database)]
  NEW --> S1[Customer service]
  NEW --> S2[Billing service]
  S1 --> NDB1[(Customer DB)]
  S2 --> NDB2[(Billing DB)]
  LDB --> CDC[Change data capture]
  CDC --> SYNC[Sync to new stores]
  SYNC --> NDB1
  SYNC --> NDB2
  S1 --> ACL[Anti-corruption layer]
  ACL --> MONO
  PROXY --> CMP[Shadow traffic comparison]

Related: System architecture diagram tool · Mermaid editor · All software & system architecture templates · All 521 templates