What happened
Cloudflare has introduced Workers Cache, a regionally tiered caching layer that sits directly in front of Worker entrypoints. Teams configure it through standard HTTP cache-control headers, making it composable with existing request pipelines without requiring proprietary APIs. Separately, AWS has made CodePipeline generally available in the Asia Pacific (New Zealand) region, designated ap-southeast-6, extending the continuous delivery service's reach to organizations operating or expanding in that geography.
Why it matters for your business
Workers Cache addresses a long-standing gap for teams running compute-heavy logic at the edge: previously, every request hit the Worker directly, driving up CPU costs and response latency. With a cache tier in front of the entrypoint, repeated requests for the same content can be served without executing Worker code, reducing both cost and time-to-first-byte. For AWS customers in New Zealand, local CodePipeline availability means CI/CD pipelines no longer need to route through distant regions, which lowers data-residency risk and can improve pipeline execution speed. Organizations subject to New Zealand data sovereignty requirements now have a compliant deployment option without architectural workarounds.
What to watch next
The composability angle of Workers Cache is worth monitoring — Cloudflare has a pattern of stacking primitives, so deeper integration with R2 storage and Durable Objects is a plausible next step. On the AWS side, the New Zealand region rollout continues a broader wave of ap-southeast expansion; additional managed services are likely to follow as AWS builds out local infrastructure to serve enterprise and government customers in the country.