Strangler fig monolith migration
Gradual migration from monolith to microservices using an API gateway to route traffic to new services as they're built.
The prompt
Strangler fig migration from monolith to microservices. Initially: all traffic routes to a Rails monolith with a PostgreSQL database. Migration: an API Gateway is introduced in front of the monolith. As each capability is extracted into a new microservice, the gateway routing rules are updated to send those URLs to the new service instead of the monolith. The new microservices have their own databases and asynchronously sync with the monolith DB during the transition via change-data-capture (Debezium → Kafka). Show three states: 1) initial monolith, 2) mid-migration with three extracted services and the gateway, 3) end state with monolith decommissioned.
What it generates
A migration diagram showing the before, during, and after states of strangler fig extraction.
When to use it
When you need to migrate off a monolith without a risky big-bang rewrite — the safest pattern for large-scale modernisation.
Generate this diagram in seconds
Copy the prompt above, sign in for free, and paste it into the generator.
Related microservices templates
API gateway with microservices
Edge API gateway routing to a microservice fleet with shared identity, async messaging, and per-service databases.
Saga pattern (orchestration)
Orchestrator-coordinated saga with compensating actions for a multi-service order placement transaction.
Event sourcing + CQRS
Event-sourced write side with append-only event store, plus separate read models materialised from event stream.