Monolith-to-Microservices Decomposition Plan
Analyze a monolith and decompose it into microservices with domain-driven boundaries, a gradual migration plan, and clear trade-offs, without inventing nonexistent frameworks or APIs.
Pro
Model: claude-sonnet-4-7
2,673 previews
0 uses
Knowledge: 2026-Q2
This prompt requires the pro plan
Upgrade plan
Your current plan: free
Planning the exit from a bloated monolith that slows deployment, identifying the first service to safely extract, preparing a decomposition document for the engineering team before starting.
#خدمات مصغّرة#تفكيك المجال#هجرة تدريجيّة#حدود الخدمات
Built-in quality guards
Anti-hallucination
No fabricated frameworks, message libraries, or APIs absent from the stack
Security Check
Each service validates input and enforces authorization with zero implicit trust
Completeness
Cover boundaries, data, communication, migration, and risks without truncation
Format Check
Adherence to the six-section structure and service/phase tables