Mathias Verraes – Advanced Domain-Driven Design
Software design can have a very slow feedback loop: by the time you find out if the architectural and design decisions you made were the right ones, it may be too late for drastic changes. As developers, we tend to phrase all problems as technical problems, which can be sufficiently challenging in their own right. We tend to lose sight of the underlying business concerns.
Domain–Driven Design is total approach to building software for complex domains. It’s a way of thinking that helps you decide how to tackle complexity, and where to focus your efforts. By putting the business at the heart of our software, and keeping our domain model closely tied to our understanding of the business, we can create value at a much deeper level.
This is what you learn In this workshop, we’ll explore this central premise of Domain–Driven Design. We’ll take a practical approach: participants will be working on real–world problems. There will be no easy answers. Instead, you’ll learn how to ask the right questions, and how to evaluate different models.
- Discovering the domain and the Ubiquitous Language
- Event Storming, conversations with Domain Experts
- Creating a model to share insights between both technical and non–technical shareholders
- Applying Systems Thinking and problem–solving techniques
- Visualizing strategic design using Bounded Contexts and Context Mapping
- Integrating with brownfield systems
- CQRS, Event Sourcing, temporal models
- Tactical Design Patterns
- Modelling exercises
- You are a Software Developer with some years of experience in working with complex domains. You’re familiar with object–oriented programming.
- It’s recommended to read “Domain–Driven Design” (Evans, 2004), but not essential.
- Laptops or other devices are not required, but useful for taking notes.
- The course is programming language agnostic.