Wrote my first X article, about something we built into @Restatedev earlier this year:
๐๐๐ฟ๐ฎ๐ฏ๐น๐ฒ ๐๐ผ๐ฟ๐ผ๐๐๐ถ๐ป๐ฒ๐ are an extension of durable execution with structured concurrency, but very fast (avg. 3ms overhead per step) on 3AZs.
It is great when you want to record many fine-grained steps in a larger task, like in a durable agent.
Say you dispatch a conversation turn as a durable function call (with queuing, limits, etc) and then within the turn you want to record inference, guardrails, tool calls with little overhead, as if it was a durable process.
https://t.co/7QHrvV2YjO
Replit Agent switched from Temporal to Restate for three main reasons
- Lower latency and cost efficiency:
Restate executes durable steps inline, adding just a few milliseconds of overhead per step. This allows Replit to make thousands of operations durable without the overhead of scheduling each one as a separate activity.
- Unique building blocks for stateful, concurrent agents:
Virtual Objects and Durable Coroutines simplify coordinating long-lived agent sessions, parallel subagents, user steering, approvals, and cancellation, and make the architecture easier to extend.
- Restate BYOC:
Fully managed deployments in Replit's own cloud account keep sensitive data private and support both its multi-tenant cloud stack and dedicated enterprise offerings.
With Restate, Replit can use fast, durable execution inside the agent loop, giving them a simpler, more resilient architecture.
Replit now runs tens of Restate cells across regions and availability zones, and handled a major promotional traffic spike of nearly 25 000 durable actions per second per cell a few weeks after migration.
Read the full story, including how Replit built its agent architecture on Restate ๐งต
Restate v1.8.1 is out ๐
๐ Smooth hand-over when migrating Kafka topics to the new Kafka integration
๐๏ธ Remove several deployments at once
โธ๏ธ Kubernetes ConfigMap changes applied without restarts
๐ Plus fixes, security updates and UI updates
https://t.co/wIZCBTZL7x
Also in 1.8: a CLI built for scripts and coding agents, with structured --json output, structured errors, and --dry-run / --yes. Plus SQL tables to inspect your vqueues and many more improvements.
Full announcement ๐
https://t.co/Ymezc6j0nk
Restate v1.8 is out ๐
The new virtual-queue scheduler is on by default, even for existing clusters.
"Why is this invocation still waiting?" Now you can see exactly why in the UI. ๐
Tweak concurrency rules live to shape your traffic wrt your budget and needs!
Proud of what we have built and excited for what we have already planned. I will shamelessly steal the mantra from old Facebook days. The journey is 1% done.
Weโve raised a $20M Series A led by Singular with participation from Redpoint Ventures and Capital One Ventures.
Restate is already powering Replit Agent, enterprise workflows at DOSS, and critical applications at Fortune 500 institutions.
Now weโre doubling down on making Durable Execution faster, more efficient and easier to operate at scale for the next generation of applications and AI agents.
๐ More on what weโre building and where weโre going next
Three years ago, we started Restate because we felt that building reliable distributed applications was just too hard. We were solving the same problems around failures, recovery, and consistency again and again.
Today, I'm excited to share that we've raised a $20M Series A led by Singular with participation from Redpoint Ventures and Capital One Ventures.
The need for solutions like Durable Execution has only grown since we started. Today, the majority of new Restate use cases are AI agents: long-running processes, coordinating across many tools and APIs, that need to keep working correctly through all sorts of failures and interruptions, coordinate sub-agents, or schedule work.
At the same time, our customers have pushed Restate into places that expanded our own view of what Durable Execution could become. Replit moved the execution of Replit Agent onto Restate. DOSS runs high volumes of enterprise workflows on Restate and Fortune 500 institutions are using Restate for complex transactional workflows.
We think this is just the beginning and excited to build what we believe will be a fundamental pillar of all infrastructure in the future.
Read more here: https://t.co/1S2AxK8Ydj
๐ Restate 1.7.3 is out!
Existing clusters can now migrate to VQueues and adopt flow control without reprovisioning.
Also included: important memory-retention, reliability, metrics, and SQL fixes.
Upgrade: https://t.co/FGXHxQd6dJ
New in Restate 1.7: Flow Control with Virtual Queues.
Define hierarchical concurrency limits for whatever matters to your workload: tenants, endpoints, agents, teams, users, etc. An invocation runs only when every matching budget has capacity.
Scoped calls now added to all SDKs
Restate 1.7 packs several other big features:
โ A revamped UI, built for applications at scale and detecting failures early
โ Better tracing tailored for extensibility and long-running agentic workloads
Restate 1.7 is out. It is the biggest release in over a year!
The star of this release is ๐ณ๐น๐ผ๐ ๐ฐ๐ผ๐ป๐๐ฟ๐ผ๐น, powered by ๐๐ถ๐ฟ๐๐๐ฎ๐น ๐พ๐๐ฒ๐๐ฒ๐.
Restate can now steer load across your the durable functions, agents, and event-driven services with flexible rules.
Together with Restate's existing capabilities for durable execution, stateful functions (virtual objects), and reliable RPC/messaging, it forms aย durable foundation for your backends and agents that goes much beyond traditional durable execution.
And all of it in a single dependency-less binary.
Read more here: https://t.co/wrH25VGmJR
Restate BYOC is officially out! All the features of Restate Cloud, but data never leaves your cloud acc.
Private, secure, and up to 10x cheaperย than traditional durable execution solutions at high volumes.
Multiple customers run it in prod with >100k durable actions/second!
Restate BYOC is officially out! All the features of Restate Cloud, but data never leaves your cloud account.
Private, secure, and up to 10x cheaperย than traditional durable execution solutions at high volumes.
Multiple customers run it in prod with >100k durable actions/sec
๐