Be proactive about state in a reactive system
summary
Reactive non‑blocking services use Kafka for async communication but lose business visibility, so the claim is to add an orchestrator to manage saga state. The demo builds a restaurant system (table, bar, kitchen) with Spring Boot/WebFlux, Zeebe (zb) workflow engine and BPMN process deployed and versioned, replacing direct producers with workers that publish Kafka messages correlated by orderId. The workflow runs, Operate shows live instances and timers, and versioning and timeouts (e.g. discounts) work as described.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:19Reactive Systems Micro Services
- 9:00Interface Spaghetti
- 9:43Saga Pattern
- 17:07Workflow Engines
- 49:04Across multiple services
related talks
01h 17mReacting to an Event-Driven World.
39mReacting to an Event-Driven World
01h 00mReacting to an Event-Driven World
14mReactive Services in practice with Webflux, Kafka and DynamoDB
58mReactive Spring
58mWelcome to the (state) machine
47mReactive Spring
28mWhen stateless APIs are not enough: deep dive into a reactive backend design