Download as PDF, PPTX
Uploaded byBernd Ruecker
JCon Live 2023 - Lice coding some integration problems
The document discusses integration patterns for microservices, emphasizing the importance of resilience and stateful retries in managing failures during processes like check-in and payment. It highlights the complexities introduced by distributed systems and the necessity of designing robust service boundaries to enhance customer experiences. The author advocates for leveraging event-driven architectures while being cautious of losing sight of larger-scale flows.
More Related Content
Similar to JCon Live 2023 - Lice coding some integration problems
![5G Explained! A High Level Overview [Introduction]](https://cdn.slidesharecdn.com/ss_thumbnails/5gexplainedahighleveloverview-260119165306-cc137a3e-thumbnail.jpg?width=640&height=640&fit=bounds)
JCon Live 2023 - Lice coding some integration problems
- 1.
- 2. Photo by Tookapic,available under Creative Commons CC0 1.0 license.
- 3. „There was anerror while sending your boarding pass“
- 4.
- 5.
- 6.
- 7. Some Service Some Service Some Service Some Service Some Service Some Service Some Service Failure will happen. Acceptit! But keep it local! Be resilient.
- 8.
- 9.
- 10. Check-in Barcode Generator Web-UI Me Output Mgmt Current situation –the bad part Stateful Retry
- 12. We are havingsome technical difficulties and cannot present you your boarding pass right away. But we do actively retry ourselves, so lean back, relax and we will send it on time.
- 13.
- 14. Check-in Barcode Generator Web-UI Me Output Mgmt Possible situation –much better! Stateful Retry
- 15. Check-in Barcode Generator Web-UI Me Output Mgmt Stateful Retry Possible situation –much better! The failure never leaves this scope!
- 16. Resulting challenges Persistent stateAsynchronous communication We will talk about why this is a good thing in a minute! Solve technical challenges (operating, scheduling, versioning, visibility, scalability, …) without accidential complexity Change the user experience
- 17.
- 18.
- 19. Check-In A workflow engineis a durable state machine Barcode REST Stateful retry
- 20. „The customer wantsa synchronous response“ Check-in Barcode Generator Web-UI Me Output Mgmt „Eh – no!“
- 21. Simple example forlive coding Credit Card Payment REST
- 22.
- 23. Payment Now you havea state machine! Credit Card REST
- 24. Do you haveto program all integration logic? 26
- 26.
- 27. Connectors Modeling Experience Low-code Forms Human Task Orchestration CAMUNDA Low-codePro-code Process Orchestration Kopfhörer
- 28.
- 29. @OutboundConnector( type = "io.camunda:http-json:1",inputVariables = {"method", ...}, ) public class HttpJsonFunction implements OutboundConnectorFunction { public Object execute(final OutboundConnectorContext context) throws Exception { final var json =; final var request = createRequest(context); return httpService.executeConnectorRequest(request); } } { "name": "REST Connector", "properties": [ { "type": "Hidden", "value": "io.camunda:http-json:1", "binding": { "type": "zeebe:taskDefinition:type" } }, { "id": "method", "label": "REST Method", "group": "endpoint", "type": "Dropdown", "value": "get", "choices": [ https://github.com/camunda/connectors-bundle/tree/main/connectors/http-json
- 30.
- 31. Runs anywhere Multiple connectorruntime options, including SaaS, self-managed, co- located, and local installations @berndruecker
- 35.
- 36.
- 37.
- 38. Payment But back tointegration logic… Credit Card REST
- 39. has to implement Retry hasto implement Idempotency Client Service Provider
- 40. Make every serviceidempotent! Credit Card Payment Charge Credit Card cardNumber amount Charge Credit Card cardNumber amount transactionId Not idempotent Idempotent charge
- 43. Don‘t worry, itwill happen safely – even if you loose connection. Feel free to reload this page any time!
- 44. Distributed systems introducecomplexity you have to tackle! Credit Card Payment REST
- 45.
- 46. It is impossibleto differentiate certain failure scenarios. Independant of communication style! Service Provider Client
- 47. Distributed systems introducecomplexity you have to tackle! Credit Card Payment REST
- 48. Distributed systems introducecomplexity you have to tackle! Credit Card Payment REST Cancel charge
- 49. retrievePayment HTTP 200 OK HTTP202 ACCEPTED Payment Happy case: Synchronous response Otherwise: asynchronous Embrace asynchronicity
- 50.
- 51. Long running capabilities areessential to design good service boundaries (= a good architecture) @berndruecker
- 52.
- 53.
- 54.
- 55. Example Order Fulfillment Payment If the credit cardwas rejected, the customer can provide new details Credit Card Retrieve Payment Rejected Rejected @berndruecker
- 56. Example Order Fulfillment Payment If the credit cardwas rejected, the customer can provide new details Credit Card Retrieve Payment Rejected Rejected @berndruecker A few smart god services tell anemic CRUD services what to do Sam Newmann
- 57. Payment failed Who is responsibleto deal with problems? Order Fulfillment Payment If the credit card was rejected, the customer can provide new details Credit Card Retrieve Payment Rejected Payment received @berndruecker
- 58. Payment failed (Potentially) long runningservices Order Fulfillment Payment Credit Card Retrieve Payment Rejected Payment received @berndruecker
- 59. Long running capabilities areessential to design good service boundaries (= a good architecture) @berndruecker
- 60. You need toredesign your customer journeys to leverage your hipster architecture! Shutterstock
- 61. Did you justsay “hipster”?
- 62. Let‘s talk aboutmessaging.
- 63. Who uses amessage bus?
- 64. Who has noproblems operating a message bus? Dead messages | No context | Inaccesible payload | Hard to redeliver | Home-grown message hospitals | …
- 65.
- 66.
- 67.
- 68.
- 69.
- 70. Did you justsay “hipster”?
- 71.
- 72.
- 73.
- 74. Phil Calcado atQCon NYC 2019
- 75. Notification Checkout Payment Inventory Shipment @berndruecker Pinball Machine Architecture „Whatthe hell just happened?“ @berndruecker
- 76. What we wanted Photoby Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0
- 77. 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
- 78. 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
- 79. 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
- 80.
- 81. Orchestration logic liveinside service boundaries
- 82. Event-driven example Inventory Payment Order Shipping CheckoutMonitor https://github.com/berndruecker/flowing-retail/ Human Tasks H2 H2
- 83.
- 84.
- 85.