No Return: Moving beyond transactions in software and in life
summary
Argues that modeling systems as atomic calls creates the transactional fallacy and the familiar spinning beach ball of death; proposes modeling as ongoing processes instead, using actor-style processes (mentions Alan Kay small talk and elixir and airline), event-first techniques like event sourcing and temporal modeling, and operational patterns such as the saga pattern, back pressure and circuit breakers. Emphasizes building observability, planning compensating actions, and favoring resilient, stateful narratives over brittle all‑or‑nothing transactions.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:34Dreams & Faith
- 5:56The Messaging Myth
- 6:54TRANSACTIONS
- 7:06THE TRANSACTIONAL FALLACY
- 7:20Processing 5461 records..
- 9:43AN ALTERNATIVE TO THE TRANSACTIONAL PERSPECTIVE
- 12:12LOOK FOR THE PROCESSES NARRATIVES
- 19:42A NARRATIVE FAILS FORWARDS
- 24:09Narrative Values
related talks
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems
52mMovin beyond request-reply: how smart APIs are different
51mComplex Event Flows in Distributed Systems
47mComplex event flows in distributed systems
50mTransactional solutions for microservices
58mImmutable Patterns of System Design; From Monolith to Agentic AI
44mDesigning for Autonomy
54mHow Events Are Reshaping Modern Systems