About This Architecture

Strangler-Fig pattern applied to payments migration across three network stages, progressively shifting traffic from monolith to dedicated payments service. Stage 1 routes all checkout traffic through the monolith; Stage 2 introduces a routing proxy with feature flags to read from the new payments service while dual-writing; Stage 3 darkens the monolith path as the payments service owns all writes. Each stage maintains network isolation via VLANs (10, 20, 30) and preserves production stability through gradual cutover. Fork this diagram to customize your own strangler migration timeline, feature flag logic, or database failover strategy.

People also ask

How do you safely migrate a payments system from a monolith to a microservice without downtime?

The strangler-fig pattern shown here uses three stages: Stage 1 keeps all traffic on the monolith, Stage 2 introduces a routing proxy with feature flags to read from the new payments service while dual-writing to both databases, and Stage 3 darkens the monolith path as the payments service takes ownership of writes. VLAN isolation and load balancing ensure production stability throughout.

Strangler-Fig Payments Migration Stages

Autoadvancedstrangler-fig-patternmicroservices-migrationnetwork-architecturefeature-flagsvlan-segmentationinfrastructure-design
Domain: NetworkingAudience: Infrastructure architects and platform engineers managing monolith-to-microservices migrations
1 views0 favoritesPublic

Created by

August 3, 2026

Updated

August 15, 2026 at 7:34 AM

Type

network

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI

AI-generated. Verify before production use. Learn more

Report this diagram