Commands and events. And intent. „Commands are all about intent. - Jonas Bonér @martinschimak Events have no intent.“ Intent Retrieve payment Payment retrieved Outcome
Commands and events. Like two sides of a coin? Payment retrieved Payment retrieval Intent Outcome Execution Something should happen Something happens Something happened Retrieve payment @martinschimak
Events to temporally decouple services ... Order summary Payment retrieved Payment UI raises projected onto Payment Service Order Service ... CQRS with „foreign“ events! @martinschimak
Events to represent history and state of systems ... Payment received Payment Payment received Payment received Payment received Payment retrieved ... Event Sourcing! @martinschimak
Events to enable whole business processes ... ... Event choreographies! Payment received Inform customer listened to by Payment Service Notification Service @martinschimak
Item ordered My context of sophisticated fulfillments Energy traded Order fulfillment Energy trade execution Coverage extension requested Policy issuance @martinschimak
New pair of shoes ordered End-to-end business processes and their phases New pair of shoes ordered Old pair of shoes worn out Order new pair of shoes New pair of shoes delivered Order Fulfillment History Customer-driven Supplier-driven Supplier-exploring Human to Machine Supporting Service Customer-determined Machine to Machine Automated Service @martinschimak
A company‘s „long-running“ order fulfillment service Order new pair of shoes New pair of shoes delivered Domain Command Domain Event “Long-running” service Order fulfillment service Supplier-driven Customer-determined Machine to Machine Automated Service @martinschimak
„Long-running“ services have long-running contracts Order new pair of shoes New pair of shoes delivered Order fulfillment service “Long-running” service “Long-running” asynchronous contract Hours to weeks @martinschimak Domain Command Domain Event
„Long-running“ services may have internal customers Retrieve payment Payment retrieved Payment service “Long-running” service Seconds to weeks @martinschimak “Long-running” asynchronous contract Domain Command Domain Event
Order Service Order placed Payment Service Payment retrieved Inventory Service Goods fetched Shipment Service Goods shipped The choreography principle @martinschimak
This is how the story is often presented … Choreo- graphy Orches- tration Process logic Process control explicit central implicit decentral Service coupling high low @martinschimak
Order Service Order placed Payment Service Payment retrieved Inventory Service Goods fetched Shipment Service Goods shipped Choreographies and their implicit process logic ... @martinschimak
Order Service Payment Service Inventory Service Shipment Service Order placed Goods shipped ... can lead to a hidden form of accidental coupling Payment Service Inventory Service Goods fetched Payment retrieved ... to change implicit process logic ... Change listener 1 ... Change listener 2 ... Change listener 3 ... @martinschimak
Payment Service Inventory Service Shipment Service Orchestration and its explicit process logic ... Order Service Fetch goods Retrieve payment Ship goods ... does not display THIS form of hidden accidental coupling...
This is how the story develops … Choreo- graphy Orches- tration Process logic Process control explicit central implicit decentral Service coupling high low Not necessarily Not necessarily @martinschimak
Let‘s dig a bit deeper and look into this ... Choreo- graphy Orches- tration Process logic Process control explicit central implicit decentral Service coupling high low Not necessarily Not necessarily @martinschimak
Payment Service Inventory Service Shipment Service Why not asynchronous commands? „Doable“ ... Order Service Fetch goods Retrieve payment Ship goods Request Async Response Request Async Response Async Response Request
How unhealthy is this apple ... Maybe Synchronous Request and Response Style Sender/Receiver Exchange Probably Transient Asynchronous by Nature Fire and Forget Style Publish/Subscribe Exchange Probably Persistent Command Event Or Asynchronous! @martinschimak
? ? ? Payment Service Inventory Service Shipment Service Why not fire the command? And listen to an event? Order Service Fetch goods Retrieve payment Ship goods Payment retrieved Goods fetched Goods shipped Order fulfilled Fire Fire Fire Listen Listen Listen
How unhealthy is this apple ... Maybe Synchronous Request and Response Style Sender/Receiver Exchange Probably Transient Asynchronous by Nature Fire and Forget Style Publish/Subscribe Exchange Probably Persistent Command Event Or Asynchronous! Like Fire and Listen? @martinschimak
? Payment Service ... we get location transparency inside a context ... Order Service Retrieve payment Payment retrieved Publish Subscribe Financial Services Bounded Context @martinschimak
? Payment Service ... and the ability to subscribe to „everything“. Order Service Retrieve payment Payment retrieved Publish Subscribe Financial Services Bounded Context Subscribe Subscribe Business Monitoring Bounded Context „Order Context wanted payment to happen!“ „Financial Context retrieved payment!“
The apple doesn’t look so unhealthy anymore ... Maybe Synchronous Request and Response Style Sender/Receiver Exchange Probably Transient Asynchronous by Nature Fire and Forget Style Publish/Subscribe Exchange Potentially Persistent Command Event Or Asynchronous! Like Fire and Listen? Like Publish and Promise to Subscribe? @martinschimak
What about focusing on semantical differences only … We specified an intent This just models our “state of mind” We use imperative tense to express intent Defined by supplier bounded context, created by customer system We created an outcome This models everybody’s “state of world” We use past tense to express an outcome Defined and created by emitter bounded context and system Command Event @martinschimak
? Payment Service Related semantics are both defined in supplier context Retrieve payment Payment retrieved Financial Services Bounded Context „When YOU send this WE promise to receive and act!“ „When WE send this YOU decide to receive and act!“ Command Event @martinschimak Make the contract explicit!
? Payment Service Mix and match decentral orchestration and choreography Retrieve payment Payment retrieved Financial Context Command Event Order Service Fulfillment Context Payment retrieval failed Event Marketing Context Customer promoted Promotions service Event @martinschimak
New pair of shoes ordered It‘s a supplier‘s responsibility to act on customer intent New pair of shoes ordered Retrieve payment Payment retrieved Domain Events Customer Supplier Payment Service @martinschimak Domain Command Domain Event
New pair of shoes ordered It‘s a customer‘s responsibility to specify intent New pair of shoes ordered Retrieve payment Domain Events Customer Supplier Order placed Order Service @martinschimak Domain Command Domain Event
New pair of shoes ordered Some responsibilities span both phases, but not all New pair of shoes ordered Promote customer Domain Events Payment retrieved Promotions service Customer promoted Promotions service @martinschimak Domain Command Domain Event
Orchestration and choreography... „it really depends“. Choreo- graphy Orches- tration Process logic Process control explicit central implicit decentral Service coupling high low Not necessarily Not necessarily Not necessarily Not necessarily @martinschimak
Embed and contain state managing business logic! Retrieve payment Payment retrieved Payment service “Long-running” service Seconds to weeks Payment retrieval failed @martinschimak Domain Command Domain Event
Why not ... persisting commands? Maybe Synchronous Request and Response Style Sender/Receiver Exchange Probably Transient Asynchronous by Nature Fire and Forget Style Publish/Subscribe Exchange Probably Persistent Command Event Or Asynchronous! Like Fire and Listen? Like Publish and Promise to Subscribe? @martinschimak
Looking behind a „long-running“ service Retrieve payment Payment retrieved Payment requested Charge credit card Depending on account balance Withdraw amount from account Amount Withdrawn Credit card charged Credit card failed Update credit card details Account details Credit card details updated Whenever card details are updated After two weeks Depending on the amount Amount credited Mark payment retrieved Mark payment canceled Payment failed Credit amount to account Whenever payment is canceled Mark payment received Payment retrieved
Credit amount back to account Withdraw amount from cust. account Charge amount by credit card I want that kind of reactive business process execution Charge amount by credit card Credit amount back to account Update credit card details Check customer account balance Payment requested Depending on account balance Charge credit card Withdraw amount from account Credit card charged Whenever credit card is charged Mark payment received Payment received Amount Withdrawn Depending on the amount Mark payment received Payment received Mark paym. partly covered Payment partly covered Whenever payment p. covered Charge credit card Credit card failed Whenever credit card failed Update credit card details Credit card details updated Whenever card details are updated Charge credit card After two weeks Mark payment canceled Payment canceled Whenever payment is canceled Credit amount to account Amount credited Every two days Remind customer Customer reminded Withdraw amount from cust. account
I want flexible and local technology decisions Order service Payment service Retrieve payment Payment retrieved Payment failed Retrieve payment Your local implementation reacting to events and commands
martinschimak
ryounasso
mot_techtalk
tomokusaba
rdmueller
tk3fftk
niftycorp
deepu105
masatoshiitoh
okuzawats
seike460
nrslib
aridlehoover
jennybc
lynnandtonic
afnizarnur
deanohume
hatefulcrawdad
swwweet
pauljervisheath
matthewcrist
yeseniaperezcruz
danielanewman
chriscoyier
csswizardry