Standalone Activities Announcement @ Replay 2026 | Durable Job Processing with Standalone Activities
summary
Standalone Activities runs a single durable job without a workflow by creating a server‑persisted activity execution that handles retries, backoff timers, heartbeats and dedupe; it ships in public preview across five SDKs and exposes the same UI and lifecycle controls as workflows. Coinbase is migrating a Redis-backed system that processes 200–600 million jobs/day across 186 namespaces to eliminate a single‑leader coordinator and gain zero job queue infrastructure plus 2 MB payloads and per‑namespace retention.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:46Standalone activities overview
- 5:18Comparison with DIY job queues
- 8:08Coinbase migration case study
- 13:03Developer experience improvements
- 18:21Next speaker introduction
- 19:31How standalone activities work
- 26:13Design rationale for job queues
- 28:01Platform features inheritance
- 32:58Code examples and SDK usage
- 36:29Getting started and resources
related talks
01h 00mReliable Agentic Systems need Durable Execution 🤖
27mSupercharging Backstage Scaffolder for Workflows
39mWorkflows, a new abstraction for distributed systems
39mAsynchronous Processing for Fun and Profity
53mDurable Execution With Restate
45mThe simplest way to build resilient applications
38mDurable Execution: The Next Leap for Microservices Architectures
45mDapr Workflows: How to Write Reliable, Fault-Tolerant Applications...