First we must start by actually collaborating with domain experts to understand the problem domain. Yes - understanding the problem space is actually really important to DDD. So we need to spend time with domain experts drawing lots of crazy diagrams on the wall, understanding the language they use, and most importantly doing lots of pretentious arm waving.
As we start to understand the problem space we can create a strategy for implementing our solution. We can start breaking the system down into smaller chunks, aligned with the problem domain (bounded contexts). We can then organise our teams around these bounded contexts to optimise for learning and delivery. As part of our strategy we can also start to design the system, using specialised Domain-Driven Architecture diagrams that communicate how our solution aligns with the problem domain (reinforcing our conceptual model).
In this session, we will explore all of these ideas.
YOU MAY ALSO LIKE:
- Strategic Domain-Driven Design Tools For Non-DDD People (SkillsCast recorded in October 2020)
- Domain-Driven Design in Practice with Michael Plöd (Online Workshop on 13th - 15th December 2022)
- Domain Driven Design in Cloud Native Environments (SkillsCast recorded in November 2022)
- Getting FP Into DDD - For Real (SkillsCast recorded in November 2022)
Strategic and Collaborative Domain-Driven Design
Nick is a technical leader, author, speaker and trainer. He helps If you need help building autonomous teams, modelling complex domains, consulting, training, or public speaking.He has a passion for delighting users, creating business impacts, crafting quality software, and building world-class engineering teams.