blog.ashleypeacock.co.uk
Developer Week 2025 Recap: Everything Cloudflare Just Shipped
Excerpt
, and Cloudflare will build and push your container image to their registry, ready to be used by your application. Now, you might be thinking: what about cold starts? Well, depending how you configure your containers, you may experience cold starts while the container boots. However, there is configuration available to set a minimum number of instances — this means Cloudflare pre-warms your containers so they are ready to serve requests immediately. Alongside prewarming, you can also set a CPU threshold that will define when your containers scale up to meet demand — meaning autoscaling is built-in to the platform. … ... On the face of it, the announcement of VPCs might not *seem* the most exciting thing ever. However, I’ve had countless conversations with companies, small and large, that want to use Cloudflare’s Developer Platform and they simply can’t — because their AWS resources, for example, are within a VPC that Cloudflare Workers cannot securely connect to. … In short, it becomes quite slow — especially if you’re executing multiple queries within a single request. That’s because each query will need to go from say Australia to Europe every single time, and additionally, you’ll need to connect to the database each time a Worker is spun up, which is quite often each time a new request comes in as Workers don’t typically hang around for long. … #### Static Asset Workers — Frameworks Go Generally Available During Birthday Week last year, Cloudflare started the migration of Pages to Workers with the release of Static Asset Workers in beta. For as long as I can remember, Pages has been the go-to option for hosting static and full-stack websites on Cloudflare. However, there were always some drawbacks with it, such as not being able to use Durable Objects without creating a separate Worker, and more recently, not having access to Workers Logs.
Related Pain Points
Workers cannot securely connect to VPC-isolated resources
8Organizations cannot use Cloudflare's Developer Platform for applications with AWS resources or other infrastructure within VPCs, as Workers lack secure connectivity to VPC-isolated environments. This is a blocker for enterprise adoption.
High latency for geographically distributed database queries from Workers
6When Workers execute multiple database queries, each request must traverse globally (e.g., Australia to Europe repeatedly), combined with per-request connection establishment, resulting in significant latency penalties.
Cold start latency when scaling from zero instances
5Railway's containerized model introduces significant cold start delays when scaling up from zero instances, affecting latency-sensitive APIs and applications with variable traffic patterns.
Pages platform lacks Workers feature parity
4Cloudflare Pages, the go-to for hosting static and full-stack websites, lacks access to features like Durable Objects (without creating separate Workers) and Workers Logs, limiting functionality compared to the Workers platform.