When you "apply" event sourcing approach to your domain's state transitions, (maybe) you don't need an OO paradigm...functional is the solution?

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
// codiceplastico
Domain Model
Service/Application Layer
Presentation Layer
Alessandro Melchiori
Storage

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

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

9. 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]