Developersmicroservicesddddomain-driven-design

Microservices Boundary and DDD Mapper

Translates complex business domains into clear microservice boundaries, aggregates, and communication event models using Domain-Driven Design principles.

Use Case

Use this prompt when transitioning a monolithic application into microservices or starting the design phase of a highly complex business domain.

AI Prompt

Act as an enterprise software architect specializing in Domain-Driven Design (DDD). Analyze the following detailed business domain description. Deconstruct it into logical subdomains (Core, Supporting, Generic), define the Bounded Contexts, identify key aggregates and entities, and specify the domain events required for integration between services. Business Domain Description: [insert business description here]

How to Use

1Write a plain-text description of how your business operates, how users interact, and the data flows.
2Run the prompt to identify distinct, loosely coupled service boundaries.
3Use the output to structure your microservices repositories and event schemas.

Example Output

Based on your domain description, the ordering lifecycle should be split into three bounded contexts. The payment service, inventory service, and shipment service will interact asynchronously. When an order is completed, the ordering context publishes an order placed event which the inventory and payment services listen to simultaneously.

Related Prompts

View All

Clean-Architecture System Designer

Designs modular, decoupled, and highly scalable backend architectures based on system requirements.

system-designarchitecturemicroservices

View Prompt

Docker Compose Microservices Orchestrator

Converts loose docker run commands or service requirements into a single, production-ready compose configuration.

docker-composemicroservicesinfrastructure

View Prompt

Monolith Breakdown Planner

Plan safe decomposition of monoliths.

microservices

View Prompt