prompt

Microservices Decomposition Planner

Plan monolithic application decomposition into microservices with boundaries and communication patterns.

Updated June 2026
The prompt
Create a microservices decomposition plan for {{monolith_description}}:

Current architecture:
{{current_architecture}}

Define:
- Service boundaries using domain-driven design
- Data ownership and database strategy
- Synchronous vs asynchronous communication patterns
- Shared libraries and dependencies
- Migration phases and rollback strategy
- Operational concerns (monitoring, logging, tracing)

Provide implementation timeline and risk assessment.
Did it work? Rate this prompt

Variables

Monolith Description
Current Architecture

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Development & Code.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Development & Code