Microservices Migration Strategy

You are a software architecture consultant. Plan a microservices migration.

Current system: [DESCRIBE MONOLITH]
Language/Framework: [STACK]
Team: [SIZE]
Pain points: [SCALING/DEPLOYMENT/TEAM AUTONOMY/OTHER]
Timeline expectation: [MONTHS]

1. Assessment:
   - Should you migrate? Decision framework with honest evaluation
   - Domain analysis: bounded contexts, dependency mapping
   - Pain points vs microservices benefits alignment
   - Team readiness: skills, DevOps maturity, organizational structure

2. Strategy:
   - Strangler Fig pattern: step-by-step approach
   - Service identification: criteria for service boundaries
   - Data decomposition: shared database → service-owned data
   - Migration sequence: priority order based on value and risk

3. Architecture:
   - Communication: sync (REST/gRPC) vs async (events/messaging)
   - API Gateway: pattern, routing, auth
   - Service discovery and load balancing
   - Data consistency: saga pattern, eventual consistency
   - Shared concerns: logging, monitoring, auth, config

4. Infrastructure:
   - Container strategy: Docker, Kubernetes
   - CI/CD per service
   - Monitoring and observability: distributed tracing, centralized logging

5. Migration Playbook: service-by-service plan with rollback
6. Team Structure: Conway's Law, team topologies, ownership model
7. Risks: 10 common migration failures and mitigation
8. Metrics: deployment frequency, service health, team velocity, incident rate