Monitoring and Orchestration of your Microservices Landscape with Kafka and Zeebe (Meetup)
•
1 like•725 views
Slides from a joined meetup of Confluent/Kafka and Camunda/Zeebe in October 2019. Code is here: https://github.com/berndruecker/flowing-retail/tree/master/kafka
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Monitoring and Orchestration of your Microservices Landscape with Kafka and Zeebe (Meetup)
Similar to Monitoring and Orchestration of your Microservices Landscape with Kafka and Zeebe (Meetup) (16)
More from Bernd Ruecker
More from Bernd Ruecker (14)
Recently uploaded
Recently uploaded (20)
Monitoring and Orchestration of your Microservices Landscape with Kafka and Zeebe (Meetup)
- 1. @berndruecker Monitoring and Orchestration of Your Microservices Landscape with Kafka and Zeebe
- 2. Berlin, Germany mail@berndruecker.io @berndruecker Bernd Ruecker Co-founder and Chief Technologist of Camunda
- 4. Simplified example: dash button Photo by 0xF2, available under Creative Commons BY-ND 2.0 license. https://www.flickr.com/photos/0xf2/29873149904/ @berndruecker
- 7. Autonomous (micro-)services Checkout Payment Inventory Shipment Dedicated Application Processes Dedicated infrastructure Dedicated Development Teams @berndruecker
- 8. Example Checkout Payment Inventory Shipment The button blinks if we can ship within 24 hours @berndruecker
- 9. Request/response: temporal coupling Checkout Payment Inventory Shipment Request Response The button blinks if we can ship within 24 hours @berndruecker
- 10. Temporal decoupling with events and read models Checkout Payment Inventory Shipment Good Stored Read Model Good Fetched The button blinks if we can ship within 24 hours *Events are facts about what happened (in the past) @berndruecker
- 14. The danger is that 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
- 15. The danger is that 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
- 16. The danger is that 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
- 17. Phil Calcado at QCon NYC 2019
- 18. API API API API API API API Microservices External Services Standard Software „What the hell just happened?“ @berndruecker
- 19. Monitoring Workflows Across Microservices https://www.infoq.com/articles/monitor-workflow-collaborating-microservices @berndruecker
- 20. Process Event Monitoring Checkout Inventory Payment Shipment Kafka Camunda Optimize @berndruecker
- 23. That‘s great
- 24. That‘s great – until you have to move…
- 25. That‘s great – until you have to move…Keep it stable, just move that one stick down there to the top. How hard can it be?
- 26. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetch the goods before the payment @berndruecker
- 27. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetch the goods before the payment Goods fetched Order placed Payment received Goods shipped @berndruecker
- 28. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0 @berndruecker
- 29. Order Extract the end-to-end responsibility Checkout Payment Inventory Shipment @berndruecker
- 31. Order Commands vs. Events Checkout Payment Inventory Shipment Order placed Retrieve payment It can still be messaging! @berndruecker
- 32. Order It is about where to decide about the coupling! Checkout Payment Inventory Shipment Order placed Retrieve payment Order decides . to listen to the event . to issue the command @berndruecker
- 33. Order Checkout Payment Inventory Shipment Stateful orchestration This orchestration requires state
- 34. A workflow engine It is currently here – so next up is… Stateful
- 35. Zeebe.io
- 37. Now it is easy to change the flow @berndruecker
- 39. Demo architecture Checkout Inventory Payment Shipment Kafka Zeebe Spring Boot Services Spring Cloud Streams Order Alternative: Kafka Connect @berndruecker
- 40. BPMN Business Process Model and Notation ISO Standard @berndruecker
- 41. BPMN supports integration use cases Aggregator Re-Sequencer Combined with timeouts: Zeebe supports Message TTL @berndruecker
- 42. BPMN supports integration use cases Compensation @berndruecker
- 45. Monolith Chaos Choreography Orchestration @berndruecker Process Monitoring Your services or applications
- 46. Your ITarchitecture Process Monitoring Monolith Chaos Choreography Orchestration Your services or applications Balance choreography and orchestration @berndruecker
- 48. Recap • In event-driven-systems it is easy to loose sight of the flow • Visibility is essential to survive • You need to balance orchestration and chorography • Distributed systems need stateful orchestration • Workflow automation is an essential building block • BPMN is very powerful and provides BizDevOps • Zeebe rocks :-) @berndruecker