For years, we’ve been operating to create construction server application simpler. We questioned how modules could be distributed, what safety guarantees a JavaScript runtime could provide, what belonged in a complete toolchain, and how easily an use could be distributed as a standalone executable. Compatibility alongside Node.js became an crucial part of that activity too: our users wanted the Deno improvements during continuing to plug into the existing JS ecosystem. The squad and community built a runtime that brought these capabilities together and challenged assumptions concerning what JS betterment could look like.
Today we’re announcing that the complete Deno squad is joining Cloudflare to obtain that activity further.
Our ambition has continually extended beyond the runtime. I wrote concerning this in my JavaScript Containers blog post: compute, storage, and communication operating together, without every application assembling its own infrastructure.
With Deno Deploy, we took another stage towards that goal. We wanted to create operating applications as straightforward as possible. But building and functioning Deploy additionally showed us how much complexity remained underneath that developer experience. I wanted to simplify that layer, too.
This led to celld. Building on the Cloudflare Workers programming model, celld lets developers build distributed applications from the commencement while making the scheme uncomplicated to operate. What excites me greatly is that the scaling is built into the programming model, fairly than infrastructure all app has to assemble itself.
The progression from Deno to Deno Deploy to celld explains why this move makes sense to us. At Cloudflare we’ll merge our activity alongside that of the Workers and Durable Objects teams. We want to create this programming example the default way to build servers, whether you run on Cloudflare’s network or your own infrastructure.
Joining additionally method choosing anywhere to concentration our effort. We’ve decided to put our future betterment activity into this shared phase fairly than continuing to develop a distinct runtime and hosting service. We cognize this is a consequential change for group who have built on Deno.
To everyone who contributed code, built businesses on Deno, reported problems, and trusted our direction: appreciate you. Here’s what this method concretely:
- We volition assistance the Deno runtime for another twelvemonth alongside monthly releases containing bug fixes and safety updates. After that twelvemonth we volition end our betterment of the Deno runtime. Deno will remain open source, and we greeted others who desire to continue its development.
- Deno Deploy volition continue functioning for six months before shutting down. We will provision immigration assistance for paying customers moving to Cloudflare Workers.
- JSR volition continue operating, alongside its infrastructure moving to Cloudflare.
- We volition continue supporting rusty_v8 and activity toward integrating it into workerd.
The need for improved abstractions is particularly acute alongside AI. Durable Objects bring together capabilities that are particularly helpful for delegate harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface. This is what I’m most enthusiastic to examine and why celld focuses on Durable Objects.
Kenton Varda and I explain additional in our joint article on the Cloudflare blog. If you’re construction agents at measure and desire to run them on your own infrastructure, delight attain me now at [email protected].
