Molto spesso si accosta, piu’ o meno inconsapevolmente, il paradigma Object Oriented, ai principi di Domain Driven Design senza porsi la domanda se qualche altro “stile” possa coesistere meglio con aggregate, value object, command e domain event. Ebbene si: c’e’ dell’altro la’ fuori… In questa sessione vedremo come un linguaggio funzionale (F# nello specifico) si presta ad una piu’ intuitiva e compatta implementazione di un bounded-context

1. Alessandro Melchiori
Functional domain driven design
// Software architect @ codiceplastico
// @amelchiori

2. Functional domain driven design
Alessandro Melchiori
// codiceplastico

3. Functional domain driven design
Alessandro Melchiori
// codiceplastico
Tackling Complexity in the Heart of Software

4. Functional domain driven design
Alessandro Melchiori
// codiceplastico

5. Functional domain driven design
Alessandro Melchiori
// codiceplastico
It’s really become clear to me in the last
couple of years that we need a new
building block and that is the Domain
Events
[Eric Evans]

6. Functional domain driven design
Alessandro Melchiori
// codiceplastico
A single model cannot be appropriate for
reporting, searching and transactional
behavior
[Greg Young]

7. Functional domain driven design
// codiceplastico
Domain Model
Service Layer
Presentation Layer
Alessandro Melchiori
Write storage
Read storage

8. Functional domain driven design
Alessandro Melchiori
// codiceplastico
State transition are an important part of our
problem space and should be modeled
within our domain
[Greg Young]