Domain-Driven Design: Modeling Complex Software Systems

Tackling Complexity in the Heart of Software

Description

This training is intended for mediors and seniors who want to work with Domain-Driven Design (DDD) in practice. You will learn the concepts of DDD and apply them in scenarios that go beyond simple examples.

Domain-Driven Design has two sides. A more process- and design-oriented side, that is what the Strategic Patterns are about, and a software-oriented side, the Tactical Patterns. Since the release of Eric Evans' 'blue book / the blue pill' in 2003 (title Domain-Driven Design), DDD has expanded enormously. All kinds of patterns related to DDD have emerged in the global community. Think of Event-driven Architecture, CQRS, Event Sourcing, Micro Services, Eventual Consistency, Event Storming, etc.

In this training all these patterns are discussed and we discuss the underlying coherence. The training goes beyond an introduction of these terms. We also look at the details, the do’s and don'ts and practical application.

The training is run during three separate days. Between these days you are expected to practice with the learned concepts. You will receive homework for this (study load half to a full day).

Program: Day 1

• Introduction
• Strategic Patterns (Ubiquitous Language, Bounded Context)
• Event Storming (Events, Commands, Definitions, External Systems, Risks, Policies, Read Models, Aggregates)
• Homework: Event Storming session applied to (part of) your project

Day 2

• Presenting and discussing homework
• Tactical Patterns (Layered architecture, Aggregates, Entities, ValueObjects, Repositories, Application Services)
• Homework: design / programming assignment

Day 3

• Presenting and discussing homework
• Strategic patterns (Context Map, Conformist, Shared Kernel, Anti-corruption Layer, ...)
• Tactical Patterns (Event Sourcing, Domian Services, Factories)
• Related Patterns (Micro Services, Eventual Consistency, CQRS, Central Event Store)

Learning Goals

• Assess to what extent DDD is useful in a specific project. [Evaluate]
• Classify and explain the strategic, tactical, and related patterns of DDD, like Ubiquitous Language, Bounded Context, Context Map, Model Integrity, Core/Supporting/Generic Domain, Event, Aggregate, Entity, Value Object, Factory, Application Service, Doamin Service, Repository, Layered Architecture, Command, Event Storming, Event Sourcing, CQRS, Eventual Consistency, Micro Services [Understand]
• Formulate and maintain a Ubiquitous Language [Create]
• Design a domain model in code [Create]
• Avoid anti-patterns like Anemic Models and Primitive Type Obsession [Apply]

Subjects

• Introduction
• Strategic Patterns
• Event Storming
• Tactical Patterns
• Related Patterns