3. WHY DO WE NEED YET ANOTHER SHINY?
Is this an Architecture? No: a bunch of patterns
Sorry I don’t cook
Less how should it be, more what should it do
4.
5. WHY DDD IS RELEVANT
Ubiquitous language
Bounded contexts
Aggregates
If you are looking for intention, there is a way to
persist it
Legacy systems anyone?
7. CQRS/ES
CQRS: “Separate command messages that
change state from query messages that read
state.”
Event Sourcing: Capture changes to an
application state as a sequence of events.
14. CONSEQUENCE
Compensating actions -> there is no big eraser
here
Automatic audit log
Since there are no queries to read… the
aggregate roots have fewer relationship and their
boundaries are better defined
15. AN EXAMPLE
1. Add Item to cart
2. The product is not in stock