Most server programs are Linux programs. They include a filesystem, some executables, and possibly some shared libraries, which may interact with system software like systemd or nsswitch.
Docker popularized the use of Linux containers; OS-level virtualization provided an excellent mechanism for distributing server software. Each container image is a dependency-free, ready-to-run package.
Because server software typically relies on many system resources and configurations, deploying it has been challenging in the past. Linux containers solve this problem.
A similar closed environment can be found in browser JavaScript , albeit at a higher level of abstraction. Cloudflare’s Zack Bloom inspired us back in 2018 to think about whether JavaScript itself could provide a new kind of self-contained server container.
The more we can remove unnecessary abstractions, the closer we can get to the notion of “the network is the computer”. Cloudflare Workers are essentially the implementation of this concept in the Cloudflare network. Deno Deploy is a new implementation (on the GCP network) of this idea.
In this post, I’ll describe my thoughts on JavaScript containers and speculate on how the technology will evolve in the coming years.
Universal scripting language
Technology is hard to predict, but the World Wide Web is sure to …
The post JavaScript Containers first appeared on Lenix Blog .
This article is reprinted from https://blog.p2hp.com/archives/9000
This site is for inclusion only, and the copyright belongs to the original author.