Zero-downtime monolith to microservices migration strategy

Create a Monolith to Microservices Migration Plan for:\\\\\\\\n\\\\\\\\nProject: [PROJECT NAME]\\\\\\\\nMonolith stack: [LANGUAGE + FRAMEWORK + DATABASE]\\\\\\\\nCode size: [LINES OF CODE / NUMBER OF DATABASE TABLES]\\\\\\\\nTeam: [NUMBER] developers in [NUMBER] squads\\\\\\\\nCurrent deployment frequency: [NUMBER] releases/week\\\\\\\\nMain monolith problems: [DESCRIBE: coupling, build time, scalability]\\\\\\\\nTarget stack (microservices): [SAME LANGUAGE / NEW LANGUAGE]\\\\\\\\nTarget infrastructure: [AWS/GCP/AZURE with Kubernetes]\\\\\\\\nConstraint: [ZERO DOWNTIME / MINIMUM AVAILABILITY OF X% / NONE]\\\\\\\\n\\\\\\\\n## PHASE 0 — PREPARATION (2-4 weeks before starting)\\\\\\\\n\\\\\\\\n**Why preparation is more important than the migration itself:**\\\\\\\\nSkipping preparation is the #1 cause of migration failure.\\\\\\\\n\\\\\\\\n**1) Monolith mapping:**\\\\\\\\n- Identify all modules and their responsibilities\\\\\\\\n- Map dependencies between modules (visualize with diagram)\\\\\\\\n- Identify which database parts are used by which modules\\\\\\\\n- Measure current test coverage (target: > 60% to begin)\\\\\\\\n- Identify the most unstable parts (most historical bugs)\\\\\\\\n\\\\\\\\n**2) Bounded Context definition (Domain-Driven Design):**\\\\\\\\n- Event Storming workshop with the team (4 hours)\\\\\\\\n- Identify business domains with clear boundaries\\\\\\\\n- Prioritize by: low coupling + business value + scale demands\\\\\\\\n- First microservice candidates: the most isolated, lowest risk\\\\\\\\n\\\\\\\\n**3) Base infrastructure (must exist before the first service):**\\\\\\\\n- Monolith containerization: Docker + working docker-compose\\\\\\\\n- CI/CD pipeline: automated tests + automated deployment\\\\\\\\n- Staging environment identical to production\\\\\\\\n- Basic observability: centralized logs + health metrics\\\\\\\\n- Service registry (if microservices need to discover each other)\\\\\\\\n\\\\\\\\n**4) API contract definition:**\\\\\\\\n- Does the monolith expose a REST/GraphQL API? Version it now\\\\\\\\n- Define event formats to be published\\\\\\\\n- Team agreement: no service accesses another service's database\\\\\\\\n\\\\\\\\n## PHASE 1 — FIRST MICROSERVICE (\\\\\\\\