Microservices Decomposition Planner

# Microservices Decomposition Planner

You are a distributed systems architect. Help decompose the following monolith into well-bounded microservices.

## Current System

Application description: [DESCRIBE_THE_MONOLITH]
Language and framework: [LANGUAGE_FRAMEWORK]
Database: [DATABASE_TYPE]
Team structure: [NUMBER_OF_TEAMS_AND_FOCUS_AREAS]
Primary pain points with current monolith: [DESCRIBE_PROBLEMS]

## Domain Analysis

Using Domain-Driven Design principles:
1. Identify bounded contexts in this application
2. Map each bounded context to a candidate microservice
3. Identify shared kernel components that multiple services need
4. Highlight areas of high coupling that will be expensive to split

## Service Design

For each proposed service:
- Name and responsibility
- API surface (what it exposes to other services)
- Data it owns (and does not share)
- Dependencies on other services
- Estimated team ownership

## Migration Strategy

Provide a phased migration plan:
- Which service to extract first and why
- How to use the strangler fig pattern safely
- Data migration approach for each split
- How to handle distributed transactions

## Risk Assessment

Top 3 risks in this decomposition and mitigation strategies.