Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation

3.897 visualizaciones

Publicado el

A company’s core business processes nearly always span more than one microservice. In an e-commerce company, for example, a “customer order” might involve different services for payments, inventory, shipping and more. But how do these services play together to fulfill the customer’s desire?

Implementing long-running, asynchronous, and complex collaborations between distributed microservices is challenging. How can we ensure visibility of cross-microservice flows and provide status and error monitoring? How do we guarantee that overall flows always complete, even if single services fail? Or how do we recognize stuck flows so that we can fix them?

In this webinar, Bernd will explain how workflow automation supports the orchestration of microservices, to make sure business processes are always carried out - even in case of failure -
providing monitoring and visibility into the overall progress and status.

He will reveal how to do all of this without introducing monolithic workflows that clash with microservices principles. You will also learn how to balance orchestration (using a workflow engine) with choreography (using events). Still believe that choreography is more loosely coupled and thus the modern way to go? You definitely need to listen in…

Publicado en: Tecnología
  • Sé el primero en comentar

Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation

  1. 1. Monitoring & Orchestrating Your Microservices Landscape using Workflow Automaton 11 March 2020
  2. 2. 2 Today’s Presenter Bernd Ruecker Co-founder & Chief Technologist, Camunda @berndruecker http://berndruecker.io/
  3. 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. 4. Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation @berndruecker
  5. 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. 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. 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/
  8. 8. Traditional enterprises cannot relax! 8 https://www.forbes.com/sites/mayrarodriguezvalladares/2019/02/14/ bigtech-poses-a-greater-threat-to-financial-institutions-than-fintech/
  9. 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. 10. And you?
  11. 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…
  12. 12. Wild West Integration
  13. 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
  14. 14. Some Service Some Service Some Service Some Service Some Service Some Service Some Service Autonomous Microservices…
  15. 15. Simplified example: dash button Photo by 0xF2, available under Creative Commons BY-ND 2.0 license. https://www.flickr.com/photos/0xf2/29873149904/ @berndruecker
  16. 16. Three steps… @berndruecker
  17. 17. (Micro-)services Checkout Payment Inventory Shipment @berndruecker
  18. 18. Order Placed Payment Received Goods Fetched Notification Checkout Payment Inventory Shipment Event-driven architecture @berndruecker
  19. 19. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched @berndruecker
  20. 20. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched @berndruecker
  21. 21. 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
  22. 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. 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. 24. Phil Calcado at QCon NYC 2019
  25. 25. API API API API API API API Microservices External Services Standard Software „What the hell just happened?“ @berndruecker
  26. 26. Process Events Monitoring Camunda Optimize Order placed Payment received Goods fetched Goods shipped @berndruecker Order placed Payment received Goods fetched Goods shipped
  27. 27. Demo
  28. 28. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetch the goods before the payment @berndruecker
  29. 29. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetch the goods before the payment Goods fetched Order placed Payment received Goods shipped @berndruecker
  30. 30. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and P..19 / CC BY-SA 4.0 @berndruecker
  31. 31. Order Extract the end-to-end responsibility Checkout Payment Inventory ShipmentPayment received Order placed Retrieve payment @berndruecker
  32. 32. 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
  33. 33. Order It is not about the protocol! Checkout Payment Inventory Shipment Order placed Retrieve payment It can still be messaging! @berndruecker
  34. 34. 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
  35. 35. Order Checkout Payment Inventory Shipment
  36. 36. Demo
  37. 37. Zalando does Sales-Order & Order-Fulfillment or every order worldwide via Camunda @berndruecker
  38. 38. Workflows live inside service boundaries @berndruecker
  39. 39. No BPM(N) monoliths https://blog.bernd-ruecker.com/avoiding-the-bpm-monolith-when-using-bounded-contexts-d86be6308d8 @berndruecker
  40. 40. Order Checkout Payment Inventory Shipment Credit Card Let‘s briefly look at payments again Customer Credits REST REST
  41. 41. BPMN enables long running interactions
  42. 42. BPMN enables long running interactions Do it reliably! Stateful retry Restore consistency
  43. 43. BPMN enables long running interactions
  44. 44. BPMN enables long running interactions
  45. 45. BPMN enables the Saga pattern
  46. 46. BPMN enables the Saga pattern
  47. 47. The payment workflow
  48. 48. Can your company leverage your hipster architecture? Shutterstock You need to change business processes and customer experience!
  49. 49. Example @berndruecker
  50. 50. Example @berndruecker sync
  51. 51. Example @berndruecker
  52. 52. It is hard to implement Payment Seat ReservationBooking Ticket Generation REST
  53. 53. It is hard to implement Payment Seat ReservationBooking Ticket Generation REST
  54. 54. Typical pattern Payment Seat ReservationBooking Ticket Generation REST Simulate synchronicty by waiting (callback or polling)
  55. 55. @berndruecker happy case failure case Redesign your business process accordingly! Or some interface to poll for status Sync in happy case Async response
  56. 56. @berndruecker Redesign your business process accordingly!
  57. 57. 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
  58. 58. Thank you! @berndruecker
  59. 59. Get started today! https://github.com/berndruecker/flowing-retail More info about Camunda and enterprise edition trial: http://camunda.com/
  60. 60. 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+
  61. 61. 8686 Camunda is helping NASA go to Mars! 2020
  62. 62. 87 Camunda Customers 87 InsuranceFinancial Services Telco Technology ‘Startups’Media
  63. 63. Q&A
  64. 64. Thank you

×