Thousands of software engineers around the world use domain-driven design to design model their domains and design software systems. This template allows them to do this remotely with Miro.
Map out your domain as a portfolio of capabilities and anticipate how they may change over time. Place a special focus on identifying the core domains, the key areas for business growth. Also show how your architecture aligns with our teams.
Are you transforming from your current architecture to a target new architecture. This version of the core domain chart helps you to trade-off risk vs value when planning your migration road map or next steps.
Bounded Contexts are software sub-systems aligned to parts of the business domain. Bounded Contexts can be implemented as microservices or as modules within a monolith.
Use the Bounded Context Canvas to design an individual Bounded Context by answering the essential the essential design questions in the canvas. Then, use the visualisation to challenge your design - do you have the right boundaries, interfaces, and dependencies?
Designing good systems is not just about finding good boundaries and precise names. Designing the interactions between components in a systems, or bounded contexts in Domain-Driven Design, is vital to create loosely-coupled systems, and loosely-coupled teams.
A large design requires many small, but significant decisions. It's important to get the choice of command, event, or query right for every interaction.
Learn more, contribute ideas, and provide feedback at github.com/ddd-crew
Do you have a great board to share with the world? We'll help you turn it into a template to share with the community.