Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation
6 likes6,778 views
The document discusses the importance of monitoring and orchestrating microservices using workflow automation, highlighting the role of developers in driving digital transformation across industries. It emphasizes the need for business agility, collaboration between services, and the balance between orchestration and choreography in managing workflows. Lastly, it presents Camunda's approach to process automation, enabling long-running interactions and efficient handling of distributed systems.
Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation
- 1. Monitoring & Orchestrating Your Microservices Landscape using Workflow Automaton 11 March 2020
- 2. 2 Today’s Presenter Bernd Ruecker Co-founder & Chief Technologist, Camunda @berndruecker http://berndruecker.io/
- 3. 3 Housekeeping • The webinar is being recorded • The recording and slides will be made available after the webinar • Please post questions via the GoToWebinar control panel
- 4. Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation @berndruecker
- 5. Software is eating the world. Marc Andreessen, Entrepreneur & Investor 2011 in „The Wall Street Journal“ „ Photo by techcrunch, available under Creative Commons BY 2.0 license.
- 6. “We are a Tech Company” Goldman Sachs CEO Lloyd Blankfein 6 https://www.bloomberg.com/view/articles/2018-02-15/lloyd-blankfein-wants-goldman-sachs-to-push-technology
- 7. 7 Today, every company is becoming a software company and developers are at the center of digital transformation; they drive business processes and functions across organizations from customer service and HR to marketing and IT. And the choices these developers make will increasingly determine value creation and growth across every industry. https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/
- 9. Change is the only constant „ We don‘t know what we will need tomorrow. But we do know that we will need something. We have to be able to move quickly! CIO of a German insurance company in 2019
- 10. And you?
- 11. Credit Card Handling Payment RESTOrder Fulfillment REST DBPaymentId Amount Status 1 100 $ Collected 2 125 $ Open Reporting of overdue payments {script} Fixing open payments Scheduler to process open payments Damn it – we need a date! …to be continued…
- 13. “People were saying that groups needed to communicate more. Jeff got up and said, ‘No, communication is terrible!’ ” https://www.fastcompany.com/50106/inside-mind-jeff-bezos-5
- 16. Simplified example: dash button Photo by 0xF2, available under Creative Commons BY-ND 2.0 license. https://www.flickr.com/photos/0xf2/29873149904/ @berndruecker
- 22. 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
- 23. 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
- 24. 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
- 25. Phil Calcado at QCon NYC 2019
- 26. API API API API API API API Microservices External Services Standard Software „What the hell just happened?“ @berndruecker
- 28. Demo
- 30. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetch the goods before the payment @berndruecker
- 31. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetch the goods before the payment Goods fetched Order placed Payment received Goods shipped @berndruecker
- 32. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and P..19 / CC BY-SA 4.0 @berndruecker
- 33. Order Extract the end-to-end responsibility Checkout Payment Inventory ShipmentPayment received Order placed Retrieve payment @berndruecker
- 34. Order Events & Commands Checkout Payment Inventory ShipmentPayment received Order placed Retrieve payment @berndruecker Event Command Fact, happened in the past, immutable Intend, Want s.th. to happen
- 35. Order It is not about the protocol! Checkout Payment Inventory Shipment Order placed Retrieve payment It can still be messaging! @berndruecker
- 36. 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
- 38. Demo
- 39. Zalando does Sales-Order & Order-Fulfillment or every order worldwide via Camunda @berndruecker
- 40. Workflows live inside service boundaries @berndruecker
- 42. Order Checkout Payment Inventory Shipment Credit Card Let‘s briefly look at payments again Customer Credits REST REST
- 43. BPMN enables long running interactions
- 44. BPMN enables long running interactions Do it reliably! Stateful retry Restore consistency
- 45. BPMN enables long running interactions
- 46. BPMN enables long running interactions
- 47. BPMN enables the Saga pattern
- 48. BPMN enables the Saga pattern
- 50. Can your company leverage your hipster architecture? Shutterstock You need to change business processes and customer experience!
- 54. It is hard to implement Payment Seat ReservationBooking Ticket Generation REST
- 55. It is hard to implement Payment Seat ReservationBooking Ticket Generation REST
- 56. Typical pattern Payment Seat ReservationBooking Ticket Generation REST Simulate synchronicty by waiting (callback or polling)
- 57. @berndruecker happy case failure case Redesign your business process accordingly! Or some interface to poll for status Sync in happy case Async response
- 58. @berndruecker Redesign your business process accordingly!
- 59. Summary • Business agility is essential to survive, this is the case for microservices • The challenges move to the collaboration of the services • Balance orchestration and choreography • Workflow engines enable long running services, Saga and help taiming distributed systems
- 61. Get started today! https://github.com/berndruecker/flowing-retail More info about Camunda and enterprise edition trial: http://camunda.com/
- 62. 85 About Camunda Camunda innovates process automation with a developer-friendly approach that is standards-based, highly scalable and collaborative for business & IT 85 Founded 2008 Employees 200+ Worldwide offices: America, Asia & Europe 5 Countries with people using Camunda 190+ Community Members 100,000+ Enterprise Customers 300+
- 63. 8686 Camunda is helping NASA go to Mars! 2020
- 64. 87 Camunda Customers 87 InsuranceFinancial Services Telco Technology ‘Startups’Media
- 65. Q&A
- 66. Thank you