The design patterns from Domain-Driven Design are gradually entering the collective consciousness of software
developers. But most of the information out there, focuses on mechanistic implementation details of the patterns: how to
make an Entity in [insert favourite programming language], how to use the Repository pattern with [insert new hot ORM], how to make immutable Value Objects in [insert legacy framework]...
Applied individually, these patterns are useful, but not giving you the full potential of Domain-Driven Design.
This one day training has a different approach. We still address the technical concerns in implementing the DDD patterns,
but the focus is on more than just structure.
Learn all about
- Why Domain-Driven Design matters
- Discovering the domain and the Ubiquitous Language
- Moving away from structural into behavioral
- How patterns like Value Objects, Entities, Aggregates, Repositories, Services, Sepcifications, and
- How they make up a domain model that expresses the business
- Where to move responsbilities between them to evolve a model
About the instructor
Mathias Verraes advises companies on building software for complex environments. This involves primarily
analysis and modelling, but also code, architecture, testing, and refactoring “unmaintainable” systems. He has
worked with clients in Finance, Automotive, Government, Logistics, E-Commerce, and more. He teaches
Domain-Driven Design courses and co-organises the DDD Europe conference. When he’s not working, he’s at home in
Kortrijk, Belgium, helping his two sons build crazy Lego train tracks.
Attendees should have a good working knowledge of at least one popular Object Oriented programming language. The course is programming language agnostic.
Some prior knowledge about other design patterns and principles (Gang of Four, SOLID, ...) helps to speed things up.
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.