2019 DACH Roadshow - Workflow Automation in Microservices Architectures
2 likes660 views
The document discusses the importance of workflow automation in microservice architectures, emphasizing that each workflow should be owned by a single microservice to prevent issuing service-oriented architecture (SOA) issues. It highlights the balance between orchestration and event-driven systems, the need for visibility and manageability, and the significance of stateful orchestration in distributed systems. The summary concludes with recommendations for monitoring and optimizing workflows through various tools.
2019 DACH Roadshow - Workflow Automation in Microservices Architectures
- 1. @berndruecker Workflow Automation in Microservice Architectures
- 2. What? Why? Microservices & Workflow Automation How? t
- 3. What? Why? Microservices & Workflow Automation How? t
- 5. Photo by born1945, available under Creative Commons BY 2.0 license.
- 6. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0
- 10. Every workflow must be owned by one microservice. No exceptions!
- 12. Otherwise you end up with SOA again! Checkout Payment Inventory Shipment Order
- 14. Workflows live inside service boundaries
- 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
- 19. 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
- 20. 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
- 21. Finding the right balance 31 Observe Microservice Paradigms ● Loose Coupling ● Autonomy ● Event Collaboration Ensure Flow Manageability • End-To-End Visibility • Meet Business Process SLA • Support Continuous Process Improvement
- 22. Tracking Checkout Inventory Payment Shipment Event Bus Workflow Engine https://www.confluent.io/kafka-summit-sf18/the_big_picture
- 23. Tracking + BI Checkout Inventory Payment Shipment Event Bus Workflow Engine Camunda Optimize Other reporting / BIO solutions
- 24. But you can start acting upon certain events
- 26. Orchestration makes it easy to change the flow
- 27. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetch the goods before the payment
- 28. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetch the goods before the payment Goods fetched Order placed Payment received Goods shipped
- 30. 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
- 32. Order Checkout Payment Inventory Shipment Stateful orchestration This orchestration requires state
- 33. Order Checkout Payment Inventory Shipment Orchestration Orchestration is independant of communication channel! This might be REST, Messaging, Event-Bus, …
- 34. Workflow Engine Typical ways of communication Checkout Payment Order Shipment Checkout Payment Order Shipment Checkout PaymentOrder Shipment Message/Event Bus REST-ish
- 35. Workflow Engine Typical ways of communication Checkout Payment Order Shipment Checkout Payment Order Shipment Checkout PaymentOrder Shipment Message/Event Bus REST-ish Pub/SubOwnership
- 37. Monitoring Checkout Inventory Payment Shipment Workflow Engine Order Workflow Engine Monitor e.g. Elastic Links back Optimize
- 39. Recap • Microservices have its merits • You need to balance orchestration and chorography • Track, monitor or manage the flow – depending on your scenario • Distributed systems need stateful orchestration • Visibility is essential to survive • Workflow automation is an essential building block, make sure to use BPMN
- 40. Microservices & Workflow Automation http://berndruecker.io/
- 41. Thank you!