Lost in transaction?
summary
Demonstrates concrete fixes and a runnable demo: synchronous REST calls block threads so add a circuit breaker (Hystrix) to fail fast; move retries into a local, persisted workflow to perform stateful retrying (Camunda engine embedded in Spring Boot) with three retries at one‑minute intervals and a 202/200 degrade‑to‑async response; shows event‑driven wiring over Kafka, external task workers pulling work, and an operator UI that replays retries. All examples are on GitHub and run live.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:05Distributed systems
- 2:14Cascading failures
- 6:25Circuit Breaker
- 7:50Fail Fast
- 15:00Workflow Engine
- 20:27Route Flow Engine
- 25:15Re retrying
- 31:26Distributed transactions
- 33:23Saga pattern
- 40:14Synchronous communication
- 41:22Demo
- 44:57Workflows
- 46:43Summary
related talks
44m3 common pitfalls in microservice integration and how to avoid them
49mThe Benefits of Orchestration in Distributed Systems
45mLive Coding Some (Microservice) Integration Problems
40mDecoupling your Springboot microservices live coded using workflow automation
01h 01mLost in transaction Strategies to manage consistency in distributed systems
52mMovin beyond request-reply: how smart APIs are different
43mFault tolerance – look, it’s possible!
33mAutomating Processes in Modern Architectures