Skip to content

Distributed Systems · Editable reference architecture

Strangler fig migration architecture

An editable strangler fig migration architecture reference showing Client → Routing facade → Legacy application and downstream dependencies. Move routes incrementally while controlling dual ownership.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Strangler fig migration architecture diagram: Client, Routing facade, Legacy application, Legacy database and their connections
Strangler fig migration architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

7 components · 7 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Strangler fig migration architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Client and reaches Legacy database through Routing facade, Legacy application. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Move routes incrementally while controlling dual ownership.

The diagram contains 7 distinct components and 7 directed relationships. A separate path connects Routing facade → New service → New database. A separate path connects Legacy application → Migration event stream → New service. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Routing facade a bounded dependency timeout and a documented failure response. For Legacy database, New database, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain strangler fig migration architecture with explicit ownership and dependency paths. Move routes incrementally while controlling dual ownership.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Client → Routing facade. Define the interaction contract and trace the resulting response or state change.
  • Routing facade → Legacy application. Define the interaction contract and trace the resulting response or state change.
  • Legacy application → Legacy database. Define the interaction contract and trace the resulting response or state change.
  • Routing facade → New service. Define the interaction contract and trace the resulting response or state change.
  • New service → New database. Define the interaction contract and trace the resulting response or state change.
  • Legacy application → Migration event stream. Define the interaction contract and trace the resulting response or state change.
  • Migration event stream → New service. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Routing facade accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Routing facade, Legacy application, Legacy database. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Restrict and audit access to Legacy database, New database; define retention and deletion requirements for the actual data.

Failure handling

Routing facade is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Routing facade in an isolated test and measure errors, recovery and any repeated side effects.

Legacy database loses or returns stale state

Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches Routing facade

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Client and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Move routes incrementally while controlling dual ownership.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 7 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Strangler fig migration architecture

Benefit
Keeps the responsibilities of Client, Routing facade, Legacy application visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain strangler fig migration architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Move routes incrementally while controlling dual ownership.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Client
Client participates in strangler fig migration architecture. Client → Routing facade. Define its contract, owner and access permissions in your implementation.
Routing facade
Routing facade participates in strangler fig migration architecture. Client → Routing facade; Routing facade → Legacy application; Routing facade → New service. Define its contract, owner and access permissions in your implementation.
Legacy application
Legacy application participates in strangler fig migration architecture. Routing facade → Legacy application; Legacy application → Legacy database; Legacy application → Migration event stream. Define its contract, owner and access permissions in your implementation.
Legacy database
Legacy database participates in strangler fig migration architecture. Legacy application → Legacy database. Define its contract, owner and access permissions in your implementation.
New service
New service participates in strangler fig migration architecture. Routing facade → New service; New service → New database; Migration event stream → New service. Define its contract, owner and access permissions in your implementation.
New database
New database participates in strangler fig migration architecture. New service → New database. Define its contract, owner and access permissions in your implementation.
Migration event stream
Migration event stream participates in strangler fig migration architecture. Legacy application → Migration event stream; Migration event stream → New service. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this strangler fig migration architecture diagram show?

It shows 7 components with the core flow Client → Routing facade → Legacy application → Legacy database. Move routes incrementally while controlling dual ownership.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.