# Domain-Driven Design: The First 15 Years

## Pitch

Fifteen years after the publication of "Domain-Driven Design: Tackling Complexity in the Heart of Software" by Eric Evans, DDD is gaining more adoption than ever. 

To celebrate the anniversary, we've asked ***prominent authors in the software design world to contribute old and new essays***.

![](/files/-MEXgzyXF0YYTDKcyDpb)

## Notes

A collaborative book sponsored by Domain-Driven Design Europe

### Discovering Bounded Context with Event Storming - Alberto Brandolini

#### Use pivotal events 

![](/files/-MEXhcSkAXFVg-umUtYE)

* “specific events which are particularly relevant for the business and mark a transition between different business phases.” 
* Candidate System boundaries

#### Heuristics 

* Look at the Business phases 
  * Follow the money 
* Look at the swimlanes 
  * Show different paths that involve different models 
* Look at the people on the paper roll 
  * “twist might happen when dealing with different personas” 
* Look at the body language 
* Listen to the actual language 
* Look at the humans in the room 
  * Different people are a great indicator of different needs which means different models

###  Domain modeling with Algebraic Data Types - Scott Wlaschin

In an algebraic type system, new types are built from smaller types in two ways” : AND types OR types

Guide to start FP for DDD

## Mind map

![](/files/-MEXiBAGkNGXfPi8IC0W)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://yoan-thirion.gitbook.io/knowledge-base/xtrem-reading/resources/book-notes/domain-driven-design-the-first-15-years.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.