Topic
Cloudflare Workers
3 episodes
-
The Agent Development Lifecycle has arrived on Cloudflare
Jessica and Cathy dig into Cloudflare packaging the messy agent workflow into something that looks a lot more like a real software lifecycle: building, tracing, testing, deploying, and maintaining agents on Workers with observability and workflow plumbing that already exists.
-
Your Worker can now have its own cache in front of it
Cloudflare launched Workers Cache, a tiered cache that sits in front of Worker code itself — not between the origin and Cloudflare. Single-line Wrangler config plus standard Cache-Control headers. On hit, Worker doesn't run (zero CPU cost); on miss, Worker runs and populates cache for the next request anywhere on Earth. The shift: Workers went from 'bolt-on transformation layer in front of origin' (2017) to 'the origin itself' (modern frameworks: Astro, Next.js, Remix, SvelteKit). Cache-in-front solves the SSR problem — server-render on demand, cache the response, refresh on TTL without build-time prerender cost. Stale-while-revalidate makes it feel instant (serve stale immediately, refresh in background). Full Vary support for content negotiation (same URL, multiple representations: WebP vs JPEG, English vs French, HTML vs JSON). Per-entrypoint cache control lets you compose caching into app structure. Available today to all Workers on any plan.
-
A closer look at Python Workflows, now in beta
Cloudflare introduces Python Workflows in beta, expanding developers' ability to automate multi-step applications using Python, a favored language for data pipelines and AI. This new feature simplifies orchestration with built-in error handling and retry behavior, making it easier to create robust workflows.