Decoupling your Springboot microservices live coded using workflow automation
summary
Live-coded refactor: three Spring Boot services get a Camunda workflow engine added, replacing an inline if and synchronous REST chain with a deployed order-process.bpmn workflow that holds state, returns immediately, and continues work asynchronously. The demo shows visual cockpit traces, Camunda BPM REST calls, a non-interrupting timer that sends “sorry we are slow” messages every 30s, and an automated retry policy (configured as retry 4 times every 30s), plus an error boundary for “no soya” — all built live and shown working.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:29Who am I
- 1:04Distribution
- 6:23Demo
- 13:23Handling response
- 16:48Testing
- 21:43Timers
- 27:58Pause
- 28:58Error boundary event
- 30:38Get from context
- 33:48Retry cycles
- 34:28Process engine
- 36:18Visualization
- 36:38Data
- 37:43Reporting
- 38:13Where to start
- 39:23Nialls participation
related talks
45mLive Coding Some (Microservice) Integration Problems
33mAutomating Processes in Modern Architectures
49mThe Benefits of Orchestration in Distributed Systems
48mLost in transaction?
46m3 Common Pitfalls in Microservice Integration
40mCommunication between (micro-)services
45mPro-Code vs Low-Code in Microservice Orchestration
54mCamunda on Microservices