Best of Serverless — June 2025

1. 1
   Article

   Fermyon·48w

   Why We Chose Rust For Spin

   Fermyon explains their decision to build Spin, an open-source serverless WebAssembly framework, using Rust. The choice was driven by Rust's synergy with the wasmtime runtime, its powerful tooling ecosystem including clap and cargo workspaces, and its ability to support extensible architecture through plugins, templates, and factors. The article highlights how Rust's type system, memory safety, and developer toolchain enabled them to create a scalable, maintainable codebase while delivering an excellent developer experience.

   51
2. 2
   Article

   Cloudflare·48w

   Containers are available in public beta for simple, global, and programmable compute

   Cloudflare Containers are now in public beta, allowing developers to deploy containerized applications alongside Workers globally. The service offers simple deployment via wrangler, automatic global distribution, on-demand scaling, and tight integration with the Cloudflare developer platform. Containers can be programmatically controlled by Workers code, support various instance sizes, and use pay-per-use pricing. Future features include autoscaling, larger instances, and deeper platform integrations.

   22

   3
3. 3
   Article

   LogRocket·50w

   Get Vercel-level deployment without Vercel-level prices

   Learn how to deploy Next.js applications to Cloudflare Workers using the OpenNext adapter as a cost-effective alternative to Vercel. The guide covers setting up a product display app, configuring GitHub CI/CD integration, and implementing image optimization with Cloudflare Images. While Vercel offers better developer experience out-of-the-box, Cloudflare provides superior performance at scale with significantly lower costs and more customization options.

   21
4. 4
   Article

   Restate·51w

   Building stateful serverless applications with Knative and Restate

   Restate is an open source Durable Execution Engine that enables building stateful serverless applications on Knative by handling state persistence, service orchestration, and failure recovery automatically. The platform records execution progress and can suspend/resume applications, allowing Knative services to scale to zero during waiting periods. Developers write sequential code that looks like regular RPC services while Restate manages distributed systems complexities like retries, state consistency, and crash recovery. The article demonstrates building a user signup flow with Virtual Objects for state management and service orchestration patterns.

   10