Cqrs es and friends

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 it be, more what should it do

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?

IF I WAS TRYING TO LEARN CQRS NOW

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.

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… the aggregate roots have fewer relationship and their boundaries are better defined

AN EXAMPLE1. Add Item to cart2. The product is not in stock

THANKS Andrea Magnorsky @silverspoon www.roundcrisis.com I wantz sleeps, its Caturday

Cqrs es and friends

by Andrea Magnorsky on May 09, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 971

Statistics

Cqrs es and friends — Presentation Transcript

http://roundcrisis.com	970
http://www.yatedo.com	1