Download as PDF, PPTX
Uploaded byBernd Ruecker
2019 - Lost in transaction
The document discusses strategies for managing consistency in distributed systems, emphasizing the importance of aggregates as consistency boundaries and the challenges of ensuring idempotency and eventual consistency. It critiques the use of distributed transactions, highlighting the preference for stateful retries and compensation patterns like the saga for handling failures. Additionally, it outlines concepts such as orchestration and choreography in event-driven architectures, providing insights into managing complex transactions effectively.
More Related Content
2019 - Lost in transaction
- 1. @berndruecker Lost in transaction? Strategiesto manage consistency in distributed systems
- 2.
- 3.
- 4. Order Order Line Item orderId customerId chargeId … productId price … Order Charge Charge chargeId amount paymentProvider transactionId …Create Charge Mark order as paid All or nothing + @berndruecker
- 5.
- 6. Aggregates = ConsistencyBoundaries Order Order Line Item orderId customerId chargeId … productId price … Order Charge Charge chargeId amount paymentProvider transactionId … You can do ACID within here Or here But not a joined ACID transaction! @berndruecker
- 7. Aggregates = ConsistencyBoundaries Order Order Line Item orderId customerId chargeId … productId price … Order Charge Charge chargeId amount paymentProvider transactionId … Own DB / autonomous technology decisions API-driven Scalability … @berndruecker
- 8. Aggregates = ConsistencyBoundaries Order Order Line Item orderId customerId chargeId … productId price … Order Charge Charge chargeId amount paymentProvider transactionId … Own DB / autonomous technology decisions API-driven Scalability … @berndruecker
- 9. Boundaries need tobe designed carefully Charge chargeId amount paymentProvider transactionId … Order Order Line Item orderId customerId chargeId … productId price …Order @berndruecker
- 10. But no implicitconstraints! Order Order Line Item orderId customerId chargeId … productId price … Order Charge Charge chargeId amount paymentProvider transactionId … Joined DB transaciton @berndruecker
- 11. There is two-phasecommit (XA)!! TX Coordinator Resource Managers Prepare Phase Commit Phase @berndruecker
- 12. Pat Helland “ Distributed SystemsGuru Worked at Amazon, Microsoft & Salesforce @berndruecker
- 13. Pat Helland Grown-Ups Don’tUse Distributed Transactions “ Distributed Systems Guru Worked at Amazon, Microsoft & Salesforce @berndruecker
- 14. Starbucks does notuse two phase commit https://www.enterpriseintegrationpatterns.com/ramblings/18_starbucks.html Photo by John Ingle @berndruecker
- 15.
- 16. That means Do A DoB Temporarily inconsistent Eventually consistent again t Consistent Local ACID Local ACID 1 aggregate 1 (micro-)service 1 program 1 resource Violates „I“ of ACID @berndruecker
- 17. Youmightknowthisfrom: Do A Do B Temporarily inconsistent Eventually consistent again t Consistent Photoby Gerhard51, available under Creative Commons CC0 1.0 license. @berndruecker
- 18. „Building on Quicksand“Paper A C I D 2.0Pat Helland @berndruecker
- 19. Associative Commutative Idempotent Distributed 2.0 (a + b)+ c = a + (b + c) a + b = b + a f(x) = f( f(x) ) „Building on Quicksand“ Paper Pat Helland @berndruecker
- 20.
- 21.
- 22.
- 23. Strategy: retry Credit Card Payment Charge CreditCard cardNumber amount Charge Credit Card cardNumber amount transactionId Not idempotent Idempotent has to be idempotent charge @berndruecker
- 24. Photo by pixabay,available under Creative Commons CC0 1.0 license. @berndruecker
- 25. Requirement: Idempotency ofservices! Photo by pixabay, available under Creative Commons CC0 1.0 license. @berndruecker
- 26. Requirement: Idempotency ofservices! Photo by Chr.Späth, available under Public Domain. @berndruecker
- 27.
- 28. It is impossibleto differentiate certain failure scenarios: Independant of communication style! Service Provider Client @berndruecker
- 29. Strategy: Cleanup Credit Card Payment charge Make sureit is not charged! Cancel charge cardNumber amount transactionId Raise payment failed @berndruecker
- 30.
- 31. Some communication challenges requirestate. @berndruecker
- 32.
- 33. Strategy: Stateful retry Credit Card Payment charge Makesure it is not charged! @berndruecker
- 34.
- 35. Berlin, Germany bernd.ruecker@camunda.com @berndruecker Bernd Ruecker Co-founderand Technologist of Camunda
- 36.
- 37. Stateful retry &cleanup Credit Card Payment REST Cancel charge @berndruecker
- 38.
- 39.
- 40.
- 41. Embedded Engine Example(Java) https://blog.bernd-ruecker.com/architecture-options-to-run-a-workflow-engine-6c2419902d91 @berndruecker
- 42. A relatively commonpattern Service (e.g. Go) Rabbit RDMS 1. Receive 4. Send additional events 2. Business Logic 3. Send response? ACK @berndruecker
- 43. „Can this handle15k requests per second?“ @berndruecker
- 44.
- 45.
- 46.
- 47. Compensation – theclassical example Saga book hotel book car book flight cancel hotel cancel car 1. 2. 3. 5.6. In case of failure trigger compensations book trip
- 48. 2 alterntive approaches:choreography & orchestration @berndruecker
- 49.
- 50. Event-driven choreography Hotel Flight Car Trip Trip failed Trip requested Hotel booked Car booked Request trip Flight failed Car canceled Hotel canceled Perform undo (cancelcar booking) Perform undo (cancel hotel) @berndruecker
- 51. The danger isthat it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker
- 52. The danger isthat it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker
- 53. The danger isthat it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker
- 54. If your transactioninvolves 2 to 4 steps, choreography might be a very good fit. However, this approach can rapidly become confusing if you keep adding extra steps in your transaction as it is difficult to track which services listen to which events. Moreover, it also might add a cyclic dependency between services as they have to subscribe to one another’s events. Denis Rosa Couchbase https://blog.couchbase.com/saga-pattern-implement-business-transactions-using-microservices-part/ @berndruecker
- 55. Implementing changes inthe process Hotel Flight Car Trip Trip failed Trip requested Hotel booked Car booked Request trip Flight failed Car canceled Hotel canceled We have a new basic agreement with the car rental agency and can cancel for free within 1 hour – do that first! @berndruecker
- 56. Implementing changes inthe process Hotel Flight Car Trip Trip failed Trip requested Hotel booked Car booked Request trip Flight failed Car canceled Hotel canceled You have to adjust all services and redeploy at the same time! We have a new basic agreement with the car rental agency and can cancel for free within 1 hour – do that first! @berndruecker
- 57. What we wanted Photoby Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0 @berndruecker
- 58.
- 59. Orchestration Hotel Flight Car Trip Trip booked Request trip Book hotel Hotel booked Car booked Flight booked Book car Book flight We have anew basic agreement with the car rental agency and can cancel for free within 1 hour – do that first! You have to adjust one service and redeploy only this one! @berndruecker
- 60. Describe orchestration withBPMN Trip Trip booked Request trip @berndruecker
- 61. The workflow isdomain logic as part of the service Trip @berndruecker
- 62. The workflow isdomain logic as part of the service Trip Payment Payment could be one step in the Trip Saga @berndruecker
- 63. Caitie McCaffrey |@caitie @berndruecker
- 64.
- 65. Clemens Vasters Architect atMicrosoft http://vasters.com/archive/Sagas.html @berndruecker
- 66. Clemens Vasters Architect atMicrosoft http://vasters.com/archive/Sagas.html @berndruecker
- 67. Clemens Vasters Architect atMicrosoft http://vasters.com/archive/Sagas.html @berndruecker
- 68. BPMN Business Process Model andNotation ISO Standard @berndruecker
- 69. Living documentation forlong-running behaviour @berndruecker
- 70. Visual HTML reportsfor test cases @berndruecker
- 71.
- 72. Fancy a DSL?Just do it! https://github.com/berndruecker/flowing-trip-booking-saga The visual get auto-generated… @berndruecker
- 73. Thoughts on thestate machine | workflow engine market @berndruecker
- 74. Thoughts on thestate machine | workflow engine market OSS Workflow or Orchestration Engines Stack Vendors, Pure Play BPMS Low Code Platforms Homegrown frameworks to scratch an itch Integration Frameworks Cloud Offerings Uber, Netflix, AirBnb, ING, … AWS Step Functions, Azure Durable Functions, … Camunda, Zeebe, jBPM, Activiti, Mistral, … PEGA, IBM, SAG, … Apache Airflow, Spring Data Flow, … Apache Camel, Balerina, … Data Pipelines @berndruecker
- 75. Does it supportstateful operations? Does it support the necessary flow logic? Does it support BizDevOps? Does it scale? @berndruecker
- 76. My personal pro-tipfor a shortlist ;-) OSS Workflow or Orchestration Engines Stack Vendors, Pure Play BPMS Low Code Platforms Homegrown frameworks to scratch an itch Integration Frameworks Cloud Offerings Data Pipelines Camunda & Zeebe @berndruecker
- 77. Recap • Aggregates =Consistency boundaries • Grown ups don‘t use distributed transactions but eventual consistency • Idempotency is super important • Some consistency challenges require state • Stateful retry & cleanup • Saga / Compensation @berndruecker
- 78.
- 79.