Know the flow! Events, commands and long-running services.

@martinschimak -> Sep 13th, 2018 -> ExploreDDD Denver

Transcript

1. Event Command Sep 13th, 2018 -> Denver -> Explore DDD Conference Know the flow! Events, commands and long-running services @martinschimak
2. Apples Oranges @martinschimak vs
3. Commands Events @martinschimak vs Retrieve payment Payment retrieved
4. vs Orchestration Choreography Long-running services
5. Why?
6. Events look into the past „An event is something that has happened in the past.“ - Greg Young Payment retrieved @martinschimak
7. Commands look into the future A command specifies something that should happen in the future. Retrieve payment @martinschimak
8. Commands and events. And intent. „Commands are all about intent. - Jonas Bonér @martinschimak Events are intentless.“ Command Retrieve payment Payment retrieved Event
9. Commands and events. Like two sides of a coin. Payment retrieved Payment retrieval Command Event Execution Something should happen Something happens Something happened Retrieve payment @martinschimak
10. Commands and events. Flipping the coin ... Payment retrieved Order fulfillment process Event Execution Something happens Something happened @martinschimak Command Something should happen Fetch goods
11. Domain events are more explicitly discussed than commands @martinschimak
12. Worker Manager @martinschimak Why?
13. Events are really simple to grasp ... Goods shipped Order placed Goods fetched Payment retrieved ... EventStorming! @martinschimak
14. EventStorming! When it starts to get interesting! :-) @martinschimak
15. Events to separate write and read models ... Order summary Payment retrieved Payment UI raises projected onto ... CQRS! @martinschimak
16. Events to temporally decouple services ... Order summary Payment retrieved Payment UI raises projected onto Payment Service Order Service ... CQRS with „foreign“ events! @martinschimak
17. Events to represent history and state of systems ... Payment received Payment Payment received Payment received Payment received Payment retrieved ... Event Sourcing! @martinschimak
18. Events to enable whole business processes ... ... Event choreographies! Payment received Inform customer listened to by Payment Service Notification Service @martinschimak
19. Let‘s just rely on events in between services! @martinschimak
20. Payment Service Credit Card Gateway @martinschimak
21. Item ordered My context of sophisticated fulfillments Energy traded Order fulfillment Energy trade execution Coverage extension requested Policy issuance @martinschimak
22. plexiti.com @martinschimak
23. 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 Job Execution History Customer-driven Supplier-driven Supplier-exploring Human to Machine Supporting Service Customer-determined Machine to Machine Automated Service @martinschimak
24. A company‘s „long-running“ order fulfillment service Order new pair of shoes New pair of shoes delivered Command Event “Long-running” service Order fulfillment service Supplier-driven Customer-determined Machine to Machine Automated Service @martinschimak
25. „Long-running“ services have long-running contracts Order new pair of shoes New pair of shoes delivered Command Event Order fulfillment service “Long-running” service “Long-running” asynchronous contract Hours to weeks @martinschimak
26. „Long-running“ services may have internal customers Retrieve payment Payment retrieved Payment service “Long-running” service Command Event Seconds to weeks @martinschimak “Long-running” asynchronous contract
27. „Long-running“ services with fine-grained contracts Charge credit card Credit card charged Credit card gateway “Long-running” service Command Event 1 to 20 seconds @martinschimak “Long-running” asynchronous contract
28. Order Service Order placed Payment Service Payment retrieved Inventory Service Goods fetched Shipment Service Goods shipped The choreography principle @martinschimak
29. Payment Service Inventory Service Shipment Service The orchestration principle Order Service Fetch goods Retrieve payment Ship goods
30. 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
31. Order Service Order placed Payment Service Payment retrieved Inventory Service Goods fetched Shipment Service Goods shipped Choreographies and their implicit process logic ... @martinschimak
32. 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
33. 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...
34. Who made the decision to use events only? @martinschimak
35. 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
36. 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
37. Unhealthy apples vs. fruity and ripe oranges š 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 @martinschimak
38. 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
39. 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
40. ? ? ? 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
41. 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
42. ? Payment Service Why not publish the command? Order Service Retrieve payment Payment retrieved Publish @martinschimak
43. ? Payment Service ... we get location transparency inside a context ... Order Service Retrieve payment Payment retrieved Publish Subscribe Financial Services Bounded Context @martinschimak
44. ? 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!“
45. 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
46. vs Apples Oranges @martinschimak
47. Hey DDD! Do you like purely semantical differences? :-) š We specified an intended job š 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 a relevant change š This models everybody’s “state of world” š We use past tense to express change š Defined and created by emitter bounded context and system Command Event @martinschimak
48. ? Payment Service Related semantics are both defined in supplier context Retrieve payment Payment retrieved Financial Services Bounded Context „When YOU publish this WE promise to subscribe and act!“ „When WE publish this YOU decide to subscribe and act!“ Command Event @martinschimak Make the contract explicit!
49. ? 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
50. 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 Command Event(s) Events Customer Supplier Payment Service @martinschimak
51. New pair of shoes ordered It‘s a customer‘s responsibility to specify intent New pair of shoes ordered Retrieve payment Command Event(s) Events Customer Supplier Order placed Order Service @martinschimak
52. New pair of shoes ordered Some responsibilities span both phases, but not all New pair of shoes ordered Promote customer Command Event(s) Events Payment retrieved Promotions service Customer promoted Promotions service @martinschimak
53. Wait. It really depends ... on semantics? @martinschimak
54. 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
55. Embed and contain state managing business logic! Retrieve payment Payment retrieved Payment service “Long-running” service Seconds to weeks Payment retrieval failed Command Event(s) @martinschimak
56. A blossoming ecosystem of saga & process managers CADENCE Baker
57. Don‘t underestimate state managing business logic... Payment retrieved Payment service Seconds to weeks Payment retrieval canceled Command Event(s) Timeout Retry Version Compensate Parallelise Retrieve payment @martinschimak
58. @martinschimak
59. @martinschimak
60. DangerZone. Experimental. Open Thinking. (Apples and Oranges.)
61. Why not ... persisting commands, too? š 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
62. Payment retrieval saga Payment requested Order fulfillment Credit card Account Withdraw amount Order placed Retrieve payment Order items @martinschimak
63. An eventsourced aggregate ... (1) public List<Event> process(RetrievePaymentCommand cmd) { return EventUtil.events( new PaymentRequestedEvent(...) ); } @martinschimak
64. An eventsourced saga pattern ... (2) public List<Event> process(RetrievePaymentCommand cmd) { return EventUtil.events( new PaymentRequestedEvent(...), new WithdrawAmountCommand(...) ); } @martinschimak
65. Payment retrieval saga Payment requested Order fulfillment Credit card Account Amount withdrawn Withdraw amount Payment partly covered Credit Card charged Charge credit card Payment retrieved Order placed Retrieve payment Order fulfilled Order items @martinschimak
66. Payment retrieval Payment requested Order fulfillment Credit card Account Amount withdrawn Withdraw amount Payment partly covered Credit Card charged Charge credit card Payment retrieved Order placed Retrieve payment Order fulfilled Order items “Fact”sourced sagas know the flow of events and commands created by itself. @martinschimak
67. “Fact”sourced sagas leverage the “event nature” of commands. Command Event @martinschimak creating! intent.
68. Why? Aggregate (Worker) Process Manager @martinschimak
69. Why? @martinschimak Process Manager Aggregate
70. medium.com/plexiti @martinschimak Thank you!