Managing Business Processes in Microservice Architecture with Spring Ecosystem
summary
Claims that replacing a central BPMS with one process orchestrator per business process — built as microservices using Spring Cloud Stream over Apache Kafka — gives independent scaling, deployment, data ownership and failure isolation; uses Kafka Streams to build read models and task lists; cites BPM market growing from $8B to $18.5B by 2025 and a real migration that enables a 5x increase in charging stations while moving to Java 11, Kubernetes and Azure, proving the approach works in production.
AI-written summary · about
chapters (7)
- 0:00Start
- 19:14SAMPLE PROCESS - EVENT STORMING
- 21:00ASYNCHRONOUS CHOREOGRAPHY
- 23:47ASYNCHRONOUS ORCHESTRATION
- 36:49PROCESS VS SERVICE OWNERSHIP
- 38:32BPM - THE BUSINESS PERSPECTIVE REVISITED
- 40:03BPM - ARCHITECTURE PERSPECTIVE REVISITED
related talks
45mDo microservices dream about CQRS ES, Kafka Stream and BPMN ?
49mThe Benefits of Orchestration in Distributed Systems
54mCamunda on Microservices
01h 01mCapability Mapping
33mAutomating Processes in Modern Architectures
01h 17mMessage Driven Microservices in the Cloud
46m3 Common Pitfalls in Microservice Integration
47mData Microservices with Spring Cloud