Microservice Decomposition Analysis

Analyze how to decompose this system step by step.

Current monolith:
{{monolith_description}}

Key modules:
{{modules}}

Business domains:
{{domains}}

Think through systematically:

1. DOMAIN BOUNDARIES: What are the natural business boundaries?

2. DATA OWNERSHIP: Which data belongs to which domain?

3. COUPLING ANALYSIS: Which modules are tightly coupled? Why?

4. CHANGE PATTERNS: Which parts of the system change together?

5. TEAM ALIGNMENT: How does the team structure map to domains?

6. TRANSACTION BOUNDARIES: Where do we need ACID transactions vs. eventual consistency?

7. COMMUNICATION PATTERNS: Sync vs. async? Event-driven?

8. EXTRACTION ORDER: Which service should we extract first? Why?

9. STRANGLER PATTERN: How do we route traffic during migration?

10. SUCCESS CRITERIA: How do we know the decomposition is working?