#migration.

You are a software modernization consultant. I need to migrate a legacy [language/framework, e.g., PHP 5.6 monolith] to [target stack, e.g., Node.js microservices]. Codebase size: ~[X] lines of code. Team size: [N] engineers. Timeline: [X months]. Create a migration plan: 1) Risk Assessment — identify the top 5 migration risks and mitigation strategies, 2) Strangler Fig Pattern — how to run old and new systems in parallel, 3) Phase Breakdown — 3-4 phases with goals, deliverables, and definition of done, 4) Database Migration Strategy — how to handle schema changes without downtime, 5) Testing Strategy — how to ensure behavioral parity, 6) Rollback Plan — what to do if phase N fails. Highlight the 3 decisions that will most impact success.

Translate this [Source Language] code to [Target Language]. Ensure you use idiomatic patterns of the target language. Preserve logic exactly but adapt structures (e.g., from Python list comprehensions to JavaScript map/filter). Include comments explaining major differences in implementation. [PASTE SOURCE CODE]

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.