I want my process back! #microservices #serverless
3 likes943 views
The document discusses the transition from traditional processes to cloud-first strategies, focusing on microservices and serverless architecture. It highlights challenges in API management, cognitive load on teams, and the importance of event-driven choreography versus orchestration in business processes. The emphasis is on leveraging managed services and redesigning workflows for better efficiency while addressing the limitations of existing monolithic systems.
I want my process back! #microservices #serverless
- 1. @berndruecker I want my process back! #microservices #serverless
- 2. Last year our strategy was cloud-ready now it is cloud-first „ „
- 4. There is this cloud-scale workflow thing… …let‘s benchmark that! @berndruecker
- 5. What I want Load Generator (Workers, BPMN, …) @berndruecker
- 6. Google Cloud Platform (GCP) Cluster Kubernetes Docker Linux What I did Load Generator (Workers, BPMN, …) JVM @berndruecker
- 7. Google Cloud Platform (GCP) Cluster Kubernetes Docker Linux What I did Load Generator (Workers, BPMN, …) JVM @berndruecker
- 8. Google Cloud Platform (GCP) Cluster Kubernetes Docker Linux What I did Load Generator (Workers, BPMN, …) JVM @berndruecker
- 9. GCP Kubernetes Cluster Kubernetes Docker Linux Docker Linux What I did Load Generator (Workers, BPMN, …) JVMJVM undifferentiated heavy lifting @berndruecker
- 11. GCP Kubernetes Cluster Kubernetes Docker Linux Docker Linux Load Generator (Workers, BPMN, …) JVMJVM undifferentiated heavy lifting @berndruecker Drone Delivery Shopfront
- 12. Cognitive load Obscure commands or arcane configuration options increase the cognitive load on team members, effectively reducing their capacity for acquiring or improving business-oriented aspects Business Capabilities Business Capabilities undifferentiated heavy lifting undifferentiated heavy lifting Work one team can do Business Capabilities „ https://techbeacon.com/app-dev-testing/forget-monoliths-vs-microservices-cognitive-load-what-matters @berndruecker
- 13. What I would love to do Load Generator Camunda CloudFaaS @berndruecker
- 14. We will build applications very differently 10 years from now. Cloud, Microservices and Serverless are here to stay. We will leverage many more managed services. @berndruecker
- 15. The era of APIs API API API API API API API API @berndruecker
- 17. Connecting the dots… API API API API API API API Microservices External Services Standard Software API Functions @berndruecker
- 23. Weaknesses: Latency creep Payment Seat ReservationBooking Ticket Generation REST 300 ms 1150 + x ms 600 ms 250 ms
- 24. Weaknesses: Availabiliy erosion Payment Seat ReservationBooking Ticket Generation REST 99 % uptime 99 % uptime 99 % uptime 96 % uptime
- 25. And it is even hard to implement Payment Seat ReservationBooking Ticket Generation REST
- 26. And it is even hard to implement Payment Seat ReservationBooking Ticket Generation REST
- 27. @berndruecker happy case failure case Redesign your business process accordingly!
- 28. @berndruecker Redesign your business process accordingly!
- 32. Phil Calcado at QCon NYC 2019
- 33. API API API API API API API Microservices External Services Standard Software „What the hell just happened?“ @berndruecker
- 34. Example: Customer Onboarding Address Check Credit Check Customer Registration requested Customer registered https://www.infoworld.com/article/3391592/how-to-tame-event-driven-microservices.html @berndruecker
- 35. Pattern: Event-Driven Choreography Address Check Credit Check Registration Customer Event Bus Registration requested Credit checked Address checked Customer registered @berndruecker
- 37. Pattern: Event-Driven Choreography Address Check Credit Check Registration Customer Event Bus Registration requested Credit checked Address checked Customer registered @berndruecker
- 39. That‘s great
- 40. That‘s great – until you have to move…
- 41. That‘s great – until you have to move…Keep it stable, just move that one stick down there to the top. How hard can it be?
- 42. Changes required for an additional check Address Check Credit Check Registration Criminal Check @berndruecker Customer Event Bus Registration requested Credit checked Customer registered Address checked
- 43. Changes required for an additional check Address Check Credit Check Registration Criminal Check @berndruecker Customer Event Bus Registration requested Credit checked Customer registered Address checked Criminal checked
- 44. Changes required for an additional check Adress Check Credit Check Registration Criminal Check @berndruecker Customer Event Bus Registration requested Credit checked Customer registered Address checked Criminal checked „Credit checks got more expensive, do that only if all other checks succeed“
- 45. What we wanted Photo by Lijian Zhang, under Creative Commons SA 2.0 License and Wikimedia Commons / CC BY-SA 4.0 @berndruecker
- 49. Comparison 2 changes criminal check can be deployed first 2 changes, criminal check can be deployed first See also https://www.infoworld.com/article/3391592/ how-to-tame-event-driven-microservices.html @berndruecker
- 51. Monolith Chaos Choreography Orchestration @berndruecker Process Monitoring Your services or applications
- 52. Your ITarchitecture Process Monitoring Monolith Chaos Choreography Orchestration Your services or applications Balance choreography and orchestration @berndruecker
- 53. @berndruecker
- 54. Final enemy API API API API API API Microservices External Services Standard Software @berndruecker API
- 55. Final enemy: TLM - The Terrible Legacy Monolith API API API API API API Microservices External Services Standard Software @berndruecker API
- 56. TLM Feature Highlights 61 ★ Clumsy user interface ★ No proper API ★ Just one big piece of code ★ New features released once per year ★ Supports only parts of our core processes ★ No transparency of those processes @berndruecker
- 57. Final enemy: TLM - The Terrible Legacy Monolith API API API API API API Microservices External Services Standard Software @berndruecker API
- 59. Going step by step API API API API API API API Microservices External Services Standard Software API API @berndruecker