Service Decomposition Options

Explore service decomposition options.

Monolith description:
{{monolith_description}}

Key modules: {{modules}}
Team structure: {{team_structure}}

## APPROACH 1: Domain-Driven Decomposition
- Split by business domains
- Identified bounded contexts
- Data ownership per domain
- Communication patterns
- Complexity: [low/medium/high]
- Alignment score: [1-10]

## APPROACH 2: Team-Oriented Decomposition
- Split by team ownership
- Each team owns a service
- Cross-team dependencies
- Conway's Law alignment
- Complexity: [low/medium/high]
- Alignment score: [1-10]

## APPROACH 3: Capability-Based Decomposition
- Split by technical capability
- Reusable platform services
- Shared vs. dedicated services
- Platform team requirements
- Complexity: [low/medium/high]
- Alignment score: [1-10]

## APPROACH 4: Strangler Pattern Incremental
- Extract one piece at a time
- Priority order for extraction
- Coexistence strategy
- Timeline to completion
- Complexity: [low/medium/high]
- Alignment score: [1-10]

## SYNTHESIS
- Recommended approach or hybrid
- First service to extract
- 6-month roadmap