Microservice Decomposer

Analyze this monolithic application and propose a microservice decomposition:

**Current monolith**: {{monolith}}
**Pain points**: {{painPoints}}
**Team structure**: {{teams}}
**Current tech stack**: {{stack}}

Provide:
1. **Domain analysis**: identify bounded contexts using Domain-Driven Design
2. **Service boundaries**: proposed services with clear responsibilities and ownership
3. **Data ownership**: which service owns which data, shared data strategy
4. **API contracts**: inter-service communication (sync REST/gRPC, async events)
5. **Migration order**: which services to extract first (highest value, lowest risk)
6. **Strangler fig plan**: how to incrementally migrate without big-bang rewrite
7. **Shared concerns**: authentication, logging, configuration, service discovery
8. **Data migration**: how to split the monolithic database
9. **Testing strategy**: contract tests, integration tests, chaos engineering
10. **Anti-patterns to avoid**: distributed monolith, shared databases, synchronous chains

Rank services by extraction priority with estimated effort.