CQRS/ES AND FRIENDSPossibly distributed systems... intentionally
WHY DO WE NEED YET ANOTHER SHINY? Is this an Architecture? No: a bunch of patterns Sorry I don’t cook Less how should i...
WHY DDD IS RELEVANT Ubiquitous language Bounded contexts Aggregates If you are looking for intention, there is a way t...
IF I WAS TRYING   TO LEARN   CQRS NOW
CQRS/ES   CQRS: “Separate command messages that    change state from query messages that read    state.”   Event Sourcin...
AND FRIENDS Eventual Consistency Messaging
QUERY   Query Side: asking a question should not change    the answer.
TASK BASED UIS
COMMAND Tell the system what to do Has a well defined intention
EVENT Occurrence If using messaging, possibility of integration.
CONSEQUENCE Compensating actions -> there is no big eraser  here Automatic audit log Since there are no queries to read...
AN EXAMPLE1.   Add Item to cart2.   The product is not in stock
THANKS Andrea Magnorsky @silverspoon www.roundcrisis.com                        I wantz sleeps, its                    ...
Cqrs es and friends
Cqrs es and friends
Cqrs es and friends
Upcoming SlideShare
Loading in …5
×

Cqrs es and friends

7,344 views

Published on

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,344
On SlideShare
0
From Embeds
0
Number of Embeds
1,196
Actions
Shares
0
Downloads
16
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Cqrs es and friends

  1. 1. CQRS/ES AND FRIENDSPossibly distributed systems... intentionally
  2. 2. 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
  3. 3. 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?
  4. 4. IF I WAS TRYING TO LEARN CQRS NOW
  5. 5. 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.
  6. 6. AND FRIENDS Eventual Consistency Messaging
  7. 7. QUERY Query Side: asking a question should not change the answer.
  8. 8. TASK BASED UIS
  9. 9. COMMAND Tell the system what to do Has a well defined intention
  10. 10. EVENT Occurrence If using messaging, possibility of integration.
  11. 11. 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
  12. 12. AN EXAMPLE1. Add Item to cart2. The product is not in stock
  13. 13. THANKS Andrea Magnorsky @silverspoon www.roundcrisis.com I wantz sleeps, its Caturday

×