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