Download as PDF, PPTX
Uploaded byBernd Ruecker
CamundaCon 2020 Keynote - The Return of Process Automation
The document discusses the return of process automation, emphasizing misconceptions about business process management (BPM) and advocating for stateful workflow engines that enhance visibility and flexibility in handling long-running business transactions. It highlights the importance of event-driven architecture and orchestration in facilitating customer experience and business agility. Additionally, the text urges leveraging the right tools and practices to optimize operations and improve communication between business and technical teams.
More Related Content
Similar to CamundaCon 2020 Keynote - The Return of Process Automation
![[BDD 2025 - Mobile Development] Crafting Immersive UI with E2E and AGSL Shade...](https://cdn.slidesharecdn.com/ss_thumbnails/md-craftingimmersiveuiwithe2eandagslshaderveronicaputrianggraini-251124030840-0c677f44-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...](https://cdn.slidesharecdn.com/ss_thumbnails/ai-buildingaisystemsthatusersandcompanieslove-251124030845-038f7732-thumbnail.jpg?width=640&height=640&fit=bounds)
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
CamundaCon 2020 Keynote - The Return of Process Automation
- 1. The Return of ProcessAutomation @berndruecker
- 2. Ehm, I amsorry, but… Was it ever really gone? @berndruecker
- 3. Wrong Perception of „BPM“ (BusinessProcess Management) @berndruecker
- 4. Google for „BPMFrameworks“
- 5. Google for „lowcode“
- 6. Models From theWild…
- 7. Models From theWild…
- 8. Models From theWild… +
- 9. Wrong Perception of BPM Complex,strategic enterprise frameworks unrealistic low-code promises proprietary centralized & monolithic unflexible @berndruecker painful
- 10.
- 11. Change is theonly 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 @berndruecker
- 12.
- 13. Credit Card Handling Payment RESTOrder Fulfillment REST DBPaymentId AmountStatus 1 100 $ Collected 2 125 $ Open Reporting of overdue payments {script} Fixing open payments Scheduler to process open payments Dang it – we need a date! …to be continued…@berndruecker
- 14. 15 Using a workflowengine instead Workflow Engine Scheduler Durable State Glue Code Credit Card Service REST Process Definition Workflow Engine: Is stateful Can wait Can retry Can escalate Can compensate Provides visibility @berndruecker
- 15.
- 16.
- 17.
- 18.
- 19. Example Order Payment If thecredit card was rejected, the customer can provide new details Credit Card Retrieve Payment Rejected Rejected @berndruecker
- 20. Payment failed Who is responsible? OrderPayment If the credit card was rejected, the customer can provide new details Credit Card Retrieve Payment Rejected Payment received @berndruecker
- 21. Payment failed Long running services OrderPayment Credit Card Retrieve Payment Rejected Payment received @berndruecker
- 22. Long running services OrderPayment Credit Card @berndruecker
- 23.
- 24.
- 25. 27 Extending Payment Options begincommit {local TX} Customer Credit Service begin commit {local TX} Credit Card Service @berndruecker
- 26. Distributed transactions usingcompensation * Compensation @berndruecker
- 27.
- 28.
- 29. Clemens Vasters Architect atMicrosoft http://vasters.com/archive/Sagas.html
- 30. Clemens Vasters Architect atMicrosoft http://vasters.com/archive/Sagas.html
- 31. Living documentation forlong-running behaviour @berndruecker
- 32.
- 33. Biz Dev Leverage state machine& workflow engine Living documentation Visibility in testing Operate with visibility and context Understand and discuss business processes Evaluate optimizations in-sync with implementation improve communication improve communication Ops @berndruecker
- 34. Visual HTML reportsfor test cases @berndruecker
- 35.
- 36. Saga Using StepFunctions https://theburningmonk.com/2017/07/applying-the-saga-pattern-with-aws-lambda-and-step-functions/
- 37.
- 38. 40 „But I don‘tcare about technical problems!“ Is this reaction technical? Would Jeff Bezos say that? @berndruecker
- 39.
- 40. Decide on fraud Findsuspicous payments Batch Workflow e.g. 1 am Batches are orthogonal to the real workflow Items flow along the workflow as they come in e.g. 11 pm Act Batches are time delayed (high latency) @berndruecker
- 41. Decide on fraud Findsuspicous payments Streaming But Stream processors are still orthogonal to the real workflow Act Streaming adds real-life capabilities and removes latency Workflow Items flow along the workflow as they come in @berndruecker
- 42. Let‘s talk about Event-DrivenArchitecture
- 43.
- 44.
- 45.
- 46.
- 47. Phil Calcado atQCon NYC 2019
- 48. Notification Checkout Payment Inventory Shipment Pinball Machine Architecture „Whatthe hell just happened?“ @berndruecker
- 49. Peer-to-peer event chains Checkout Payment Inventory Shipment Order placed Payment received Goods shipped Goods fetched Fetchthe goods before the payment @berndruecker
- 50. Peer-to-peer event chains Checkout Payment Inventory Shipment Fetchthe goods before the payment Goods fetched Order placed Payment received Goods shipped @berndruecker
- 51. What we wanted Photoby Lijian Zhang, under Creative Commons SA 2.0 License and Wikimedia Commons / CC BY-SA 4.0 @berndruecker Choreography
- 52. Why is itso tempting? Service A Event Bus A B Service B C Service C D E F Service D G Service … Service … Service … Service … Service … Service … Service … @berndruecker
- 53. Why is itso tempting? Service A Event Bus A B Service B C Service C D E F Service D G Service … Service … Service … Service … Service … Service … Service … Adding is easy! You can „buy“ a shorter initial time-to-value by choreography. It yields in technical debt. @berndruecker
- 54.
- 55. Order Orchestration Checkout Payment Inventory Shipment Order placed Retrieve payment It can stillbe messaging! @berndruecker
- 56.
- 57.
- 58. Now it iseasy to change the process flow @berndruecker
- 59. Processes are domainlogic that live inside boundaries @berndruecker
- 60.
- 61. 67 Orchestrate anything Payment This mightbe a microservice, an RPA bot, a human, a device, a function or any other software component @berndruecker
- 62. 68 Time-to-value Customer Experience Business Agility Developer friendly BusinessITCollaboration Open Architecture OrchestrateAnything FacilitateBusinessOutcome Usetherighttooling Solve Problems Long Running Technical Business Transactions, Saga Visibility Process Automation @berndruecker
- 63. 69 Want to learnmore? https://learning.oreilly.com/get-learning/?code=PPAER20
- 64.
- 65.
- 66.