Download to read offline
Uploaded byBernd Ruecker
JavaLand 2023 - Process Oriented Integration
The document discusses speeding up the bank account opening process. It identifies three key issues with the current process: 1) a lack of end-to-end automation where local automations are not integrated, 2) a lack of understanding of the full end-to-end process as key metrics are difficult to track, and 3) a lack of flexibility to change the process as it could impact multiple systems.
JavaLand 2023 - Process Oriented Integration
- 2. We need tospeed up our bank account opening.
- 5. 1. A brokenend-to-end automation Local automations are not integrated with one another, the end-to-end process is not fully automated. Lack of understanding The end-to-end process is not fully visible and key metrics are hard to track. 2. Lack of flexibility Changing the end-to-end process is difficult since it leads to potential changes in many different systems. 3.
- 9. No problem! Just code inSpring Boot!
- 11.
- 12. Runs anywhere Supports any programminglanguage Available as a SaaS service Manage it yourself (in your own cloud, your datacenter, your laptop) Clients for Java, C#, NodeJS, Go, … available Natively integrates into your stack
- 13. Runs anywhere Multiple connectorruntime options, including SaaS, self-managed, co- located, and local installations
- 18. Connectors Modeling Experience Low-code Forms Human Task Orchestration CAMUNDA Low-codePro-code Process Orchestration Kopfhörer
- 19. Local automations or individualsautomating parts of their job No IT project Organizations automate their most critical core processes Full IT projects, Continuous Delivery Smaller, probably department internal processes IT project often hard to justify
- 20. or or or Just code in Spring Boot! Localautomations or individuals automating parts of their job No IT project Organizations automate their most critical core processes Full IT projects, Continuous Delivery Smaller, probably department internal processes IT project often hard to justify
- 21. https://camunda.com/customer/goldman-sachs/ … easy workflows like “Approveaccess or entitlement” … … payment processing …
- 22. Developer experience –many possibilities Source Code Modeler Repository CI/CD Pipeline Desktop App Web API Runtime Platform API Local filesystem We are thinking about this… Normal app deployment
- 23.
- 25. We need tospeed up our bank account opening.
- 27. A Typical AdoptionJourney Human work Human task orchestration Backend integration e.g. via API Frontend integration e.g. via RPA More task automation e.g. using DMN or machine learning Task Automation Process Orchestration @berndruecker
- 28. Is this hipsterenough?
- 29.
- 30.
- 31.
- 32. Phil Calcado atQCon NYC 2019
- 33. Notification Checkout Payment Inventory Shipment @berndruecker Pinball Machine Architecture „Whatthe hell just happened?“ @berndruecker
- 34.
- 35. 1. A brokenend-to-end automation Local automations are not integrated with one another, the end-to-end process is not fully automated. Lack of understanding The end-to-end process is not fully visible and key metrics are hard to track. 2. Lack of flexibility Changing the end-to-end process is difficult since it leads to potential changes in many different systems. 3.
- 37. Source: Talk atCamunda Con 2020 (https://blog.bernd-ruecker.com/process-automation-in-harmony-with-rpa-720effdb0513) @berndruecker
- 38. Source: Talk atCamunda Con 2020 (https://blog.bernd-ruecker.com/process-automation-in-harmony-with-rpa-720effdb0513) @berndruecker
- 39. What do thosescenarios have in common?
- 42. Those scenarios lackoversight how the dots connect!
- 43.
- 44. Processes are domainlogic and live inside service boundaries @berndruecker
- 45. PaaS operations arecentralized - Orchestration logic is not Microservice A Orchestration Engine Microservice B Microservice C Orchestration Engine Ideally SaaS (probably self-managed) Every microservice (process solution) owns its process model, glue code, and any additional artifacts Orchestration Engine
- 46.
- 47.