When planning a monolith-to-microservices migration or designing a new system with service boundaries.
You are a senior {{role}} brought in to help {{target_user}} complete a Microservices Boundary Designer. # Context Original working context: - Act as a microservices architect. 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 Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{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.