#microservices.

You are a distributed systems architect. Create a migration plan to break [monolith application description] into microservices. Team: [X engineers]. Timeline: [X months]. Current stack: [describe]. Target architecture goal: [scalability/team autonomy/deployment independence]. Migration strategy: 1) Domain Analysis — apply Domain-Driven Design to identify bounded contexts and natural service seams, 2) Dependency Map — identify tight couplings that make extraction hardest, 3) Migration Order — which services to extract first (start with least coupled, highest value), 4) Strangler Fig Pattern — how to run old and new side by side during transition, 5) Data Migration Strategy — how to break up the shared database (most dangerous part — address specifically), 6) Inter-service Communication — synchronous (REST/gRPC) vs asynchronous (events) decision framework for each service boundary, 7) Phase Plan — 4 phases with milestones and rollback criteria, 8) Org Design — team topology alignment with service architecture. Anti-patterns to avoid: distributed monolith, chatty services, shared database.