Stateful Applications in the Age of Durable Execution
summary
Durable execution engines like ReState (and alternatives such as Temporal or Azure Durable Functions) provide single-writer per key semantics and exactly-once processing, letting a durable function serialize updates, suspend for long waits and resume without lost or duplicate updates. Use per-entity virtual objects (or time-limited workflows) to event‑source a bike’s history with immediate consistency; push aggregated queries to an external store to avoid hot‑key contention; plan handler versioning for backward compatibility and rely on built-in traces for observability.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:46What and why durable execution
- 8:09Durable function workflow
- 13:14Virtual objects for state
- 18:09Bike aggregate implementation
- 21:41Observability and versioning
- 23:28Key takeaways and summary
- 25:16Q&A session
related talks
44mThe Simplest Way to Build Resilient Applications
35mBuilding resilient applications with Durable Execution
06mDurable Executions in the Face of (some) Failures
48mThe simplest way to build resilient applications
15mDurable Functions: Semantics for Stateful Serverless
32mWhy idempotency matters during durable execution in modern software stacks
45mThe simplest way to build resilient applications
37mState of Affairs or Affairs of State