Building resilient applications with Durable Execution
summary
Durable Execution uses Restate as a proxying engine and SDK to persist per-invocation logs, replay progress and drive retries; the demo builds a Java e‑commerce backend that tracks shopping carts, stores secrets in the log for email verification, and ensures exactly once payment and durable webhooks. The demo injects a failing call with a 50% crash rate, shows Restate retrying and restoring state via CTX.run, exposes itempotency header behavior, and runs as a single binary (BSL) that successfully recovers and completes workflows.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:42Challenges in resiliency
- 4:16Durable execution concept
- 10:30Hands-on demonstration
- 17:29Advanced workflow demo
- 21:59Key features review
- 24:04Architecture and ecosystem
- 25:55Use cases and closing
- 29:19Q&A session
related talks
44mThe Simplest Way to Build Resilient Applications
48mThe simplest way to build resilient applications
45mThe simplest way to build resilient applications
27mThe simplest way to build resilient applications
06mDurable Executions in the Face of (some) Failures
28mStateful Applications in the Age of Durable Execution
32mWhy idempotency matters during durable execution in modern software stacks
48mLost in transaction?