migrate-monolith-to-microservices - Migrate a Monolith to Microservices
Guides incremental monolith decomposition using the strangler fig pattern, covering domain analysis, service extraction, communication, data migration, deployment, and operations.
Tags
Updated: 2026-09-30Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Analyze monolith domains
- Sequence service extraction
- Design service communication
- Extract application services
- Configure deployment infrastructure
- Implement service observability
- Validate API contracts
- Execute service cutovers
Inputs
- Application source code
- Architecture diagrams
- Database schemas
- Entity relationships
- Business domain knowledge
- Business priorities
- Risk tolerance
- Deployment maturity
- Service boundary definitions
- Consistency requirements
- Existing deployment infrastructure
- Monitoring stack
- API contracts
- Known failure modes
- Production traffic patterns
- Stakeholder cutover approval
Outputs
- Bounded context map
- Event storming results
- Dependency graph
- Prioritized extraction sequence
- Facade architecture design
- Migration roadmap
- API contracts
- Event schemas
- Communication decision matrix
- Service codebase
- Database migration scripts
- Facade routing configuration
- Dockerfile
- Kubernetes manifests
- CI/CD pipeline
- Metrics dashboard
- Distributed tracing configuration
- Structured logging
- Contract test suite
- Resilience test results
Requirements
- Running monolith with production traffic
- Source code and database access
- Monitoring and logging infrastructure
- Team migration alignment
- Executive sponsorship
- Distributed systems experience