Monitoring and Orchestration of your Microservices Landscape with Kafka and Zeebe (Meetup)
•
6 likes•1,775 views
Slides from a joined meetup of Confluent/Kafka and Camunda/zeebe
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) (20)
More from Bernd Ruecker
More from Bernd Ruecker (20)
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. Data, data, data, … Source: Microservices orchestration survey, July 2018, 354 responses @berndruecker
- 10. Example Checkout Payment Inventory Shipment The button blinks if we can ship within 24 hours @berndruecker
- 11. Request/response: temporal coupling Checkout Payment Inventory Shipment Request Response The button blinks if we can ship within 24 hours @berndruecker
- 12. 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
- 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. 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
- 18. 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
- 19. Monitoring Workflows Across Microservices https://www.infoq.com/articles/monitor-workflow-collaborating-microservices @berndruecker
- 20. Typical approachesDistributed Tracing Data Lake / Event Monitoring Process Mining Process Tracking @berndruecker
- 22. Tracking + BI Checkout Inventory Payment Shipment Kafka Zeebe Camunda Optimize Other reporting / BIO solutions @berndruecker
- 23. Tracking + BI Checkout Inventory Payment Shipment Kafka Zeebe Camunda Optimize Other reporting / BIO solutions @berndruecker
- 24. Tracking + BI Checkout Inventory Payment Shipment Kafka Zeebe Camunda Optimize Other reporting / BIO solutions This is totally non-invasive But also limited in power @berndruecker
- 26. Zeebe.io
- 28. We do two workflow engines Camunda ZeebePersistent State Persistent change RDMS
- 29. Demo architecture Checkout Inventory Payment Shipment Kafka Zeebe Spring Boot Services Spring Cloud Streams Kafka Connect Operate @berndruecker
- 30. But you can start acting upon certain events @berndruecker
- 31. Vodafone, Liongate & WDW Presented at CamundaCOn Berlin 2018 @berndruecker
- 32. What we currently build with some customers… Camunda Optimize Elastic 17 Registration requested Credit checked Address checked Customer registered @berndruecker
- 33. Stefan Tilkov: Microservice Patterns & Antipatterns - MicroXchg 2018 @berndruecker
- 34. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetch the goods before the payment @berndruecker
- 35. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetch the goods before the payment Goods fetched Order placed Payment received Goods shipped @berndruecker
- 36. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0 @berndruecker
- 37. „Challenges?“ Source: Microservices orchestration survey, July 2018, 354 responses https://camunda.com/microservices-orchestration-survey-results-2018/ @berndruecker
- 38. Order Extract the end-to-end responsibility Checkout Payment Inventory Shipment *Commands have an intent about what needs to happen in the future Payment received Order placed Retrieve payment @berndruecker
- 39. 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
- 40. Order It is about where to decide about the coupling! Checkout Payment Inventory Shipment Order placed Retrieve payment It can still be messaging! @berndruecker
- 41. Order Checkout Payment Inventory Shipment Stateful orchestration This orchestration requires state @berndruecker
- 43. Now it is easy to change the flow @berndruecker
- 45. Demo architecture Checkout Inventory Payment Shipment Kafka Zeebe Spring Boot Services Spring Cloud Streams Order Alternative: Kafka Connect @berndruecker
- 46. BPMN Business Process Model and Notation ISO Standard @berndruecker
- 47. BPMN supports integration use cases Aggregator Re-Sequencer Combined with timeouts: Zeebe supports Message TTL @berndruecker
- 48. BPMN supports integration use cases Compensation @berndruecker
- 50. Hybrid architectures Order Credit Card Customer Credit Payment Pub/Sub e.g. Kafka Pub/Sub Work Distribution e.g. External Task Request/Response e.g. REST @berndruecker
- 51. Order Checkout Payment Inventory Shipment Every service owns its workflow! @berndruecker
- 52. Finding the right balance 61 Observe Microservice Paradigms ● Loose Coupling ● Autonomy ● Event Collaboration Ensure Flow Manageability • End-To-End Visibility • Meet Business Process SLA • Support Continuous Process Improvement @berndruecker
- 54. @berndruecker Kafka Zeebe low latency, high-throughput low frequency, latency doesn‘t matter What people think workflow automation can do What we currently teach workflow automation to be able to do What workflow automation can already do today Workflow Automation at scale
- 56. @berndruecker
- 57. 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