(Illustration: Brazil’s largest port, Port of Santos, provides container loading and unloading services. Image source: Photo by sergio souza on Unsplash。)
✳️ tl;dr
- Cloudflare Containers 1 enters public beta, immediately available for paid users with full Workers integration.
- Region: Earth global deployment, containers start in seconds, developers don’t need to select regions.
- Through Worker→Container binding, dynamically generates isolated instances by ID, suitable for multi-tenant platforms.
- Three instance types: dev/basic/standard covering 256 MiB, 1 GiB, 4 GiB memory requirements.
- 10ms billing granularity with separate CPU, memory, and disk metering, plus free tier included.
- Built-in Metrics/Logs retained for 7 days, supports external LogSink, reducing observability integration costs.
- Upcoming:
autoscale = true
enables global auto-scaling and latency-aware routing.
- Cloudflare Containers runs on AWS-developed open-source Firecracker microVM 2 with KVM isolation, reducing multi-tenant side-channel risks while maintaining startup speed and resource efficiency.
- Firecracker microVM: < 125ms cold start, < 5 MiB memory, balancing security and density.
- Ernest Chiang demonstrated 3 running 4,000 microVMs in 90 seconds on i3.metal at COSCUP 2020 Firecracker workshop.
✳️ Knowledge Graph
(More about Knowledge Graph…)
✳️ Further Reading
https://blog.cloudflare.com/containers-are-available-in-public-beta-for-simple-global-and-programmable/ ↩︎
https://www.ernestchiang.com/en/posts/2020/playing-with-firecracker/ ↩︎
https://securitybrief.com.au/story/cloudflare-launches-containers-beta-for-flexible-edge-computing ↩︎
https://blog.cloudflare.com/introducing-workers-durable-objects/ ↩︎
https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/ ↩︎