Back to all summaries

Rearchitecting the Workflows control plane for the agentic era

Luís Duarte, Mia Malden, André Venceslau
Agents Week Agents Durable Objects Cloudflare Workers Developer Platform Developers

AI-Generated Summary: This is an automated summary created using AI. For the full details and context, please read the original post.

Rearchitecting the Workflows Control Plane for the Agent-Centric Era

Cloudflare has announced significant updates to its Workflows control plane, designed to support the growing demand for agent-triggered workflows. As agents become persistent and autonomous infrastructure, operating on behalf of users for hours or days, they require a durable, asynchronous execution engine. Workflows provides this, with every step independently retryable, and each instance surviving failures without losing progress.

Key Updates and Improvements

  • Increased Concurrency: The new control plane supports 50,000 concurrent instances, up from 4,500, allowing developers to scale their agents and applications on Workflows.
  • Faster Instance Creation: 300 instances can now be created per second per account, up from 100.
  • Queued Instances: The limit for queued instances has been increased to 2 million per workflow, up from 1 million.
  • Redesigned Control Plane: The new control plane is built on two new components, designed to horizontally scale the system and alleviate bottlenecks introduced by the original architecture.

Technical Details

The Workflows control plane is built on top of Durable Objects, a simple but powerful primitive for coordination and storage within a distributed system. The new control plane uses a 1:1 ratio of Engine Durable Objects to workflow instances, and an Account Durable Object to manage all workflows and instances for an account. The redesign of the control plane has allowed for a significant increase in scalability and performance, making it easier for developers to build and deploy agent-centric applications on Workflows.

Want to read the full article?

Read Full Post on Cloudflare Blog