JavaLand 2023 - Process Oriented Integration
0 likes22 views
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 to speed up our bank account opening.
- 5. 1. A broken end-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 in Spring Boot!
- 11. Example
- 12. Runs anywhere Supports any programming language 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 connector runtime options, including SaaS, self-managed, co- located, and local installations
- 18. Connectors Modeling Experience Low-code Forms Human Task Orchestration CAMUNDA Low-code Pro-code Process Orchestration Kopfhörer
- 19. Local automations 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
- 20. or or or Just code in Spring Boot! Local automations 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 “Approve access 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
- 25. We need to speed up our bank account opening.
- 27. A Typical Adoption Journey 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 hipster enough?
- 32. Phil Calcado at QCon NYC 2019
- 33. Notification Checkout Payment Inventory Shipment @berndruecker Pinball Machine Architecture „What the hell just happened?“ @berndruecker
- 35. 1. A broken end-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 at Camunda Con 2020 (https://blog.bernd-ruecker.com/process-automation-in-harmony-with-rpa-720effdb0513) @berndruecker
- 38. Source: Talk at Camunda Con 2020 (https://blog.bernd-ruecker.com/process-automation-in-harmony-with-rpa-720effdb0513) @berndruecker
- 39. What do those scenarios have in common?
- 42. Those scenarios lack oversight how the dots connect!
- 44. Processes are domain logic and live inside service boundaries @berndruecker
- 45. PaaS operations are centralized - 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. Summary