When planning a monolith-to-microservices migration or designing a new system with service boundaries.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: System Design & Architecture - Use case: Microservices Boundary Designer - Source task: - I have a monolith that does {{describe_the_system}}. I want to decompose it into microservices. - Step 1: identify the bounded contexts using Domain-Driven Design principles. - Step 2: define service boundaries : what each service owns, its API contract, and its data store. - Step 3: identify the hardest decomposition challenges (shared data, distributed transactions, tight coupling). - Step 4: recommend a strangler fig migration plan : which service to extract first and why. - Step 5: flag services that should NOT be separated (over-decomposition risks). # Goal Bounded context map, service definitions with API contracts, decomposition challenges, strangler fig plan, and over-decomposition warnings. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Bounded context map, service definitions with API contracts, decomposition challenges, strangler fig plan, and over-decomposition warnings.
{{double-curly}} with your real context.When planning a monolith-to-microservices migration or designing a new system with service boundaries.
Extract the service with the most independent data store first — services that share databases are the hardest to separate and should come last.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.