Cloudflare Durable Objects pending I/O keep-alive guide
From 2026-10-01, pending I/O keeps Cloudflare Durable Objects in memory after the client leaves. What counts, the 15-minute limit, flags and billing.
Reliability is how well a system keeps doing its job when parts of it fail, and every production system has parts that fail. It covers the targets you set, such as SLOs and error budgets, and the platform behaviour you design around: timeouts, retries, eviction, cold starts and limits.
These guides are for engineers building on serverless and managed platforms, where much of that behaviour belongs to the provider. They explain how specific primitives behave in production, such as Durable Objects staying in memory while I/O is pending, event streams on object storage and multi-node GPU clusters, and what that means for your design. Each guide covers setup, the limits to plan for, what it costs and how to tell from your own telemetry that it works as intended.
How Polylane works on these platforms: Cloudflare and Modal.
From 2026-10-01, pending I/O keeps Cloudflare Durable Objects in memory after the client leaves. What counts, the 15-minute limit, flags and billing.
Cloudflare K2, announced 1 October 2026, is a serverless event stream on R2. What it is, how it differs from Queues, setup steps and beta limits.
Modal Clusters went GA on 1 October 2026. How @modal.clustered and rdma=True work, how to run torchrun or Ray across nodes, and the limits to plan for.