Will Cloud-Native WebAssembly Replace Docker?
Holding a brand new form, WebAssembly excels in its portability, small size, fast loading, and compatibility. Given its good security, compatibility, high efficiency, and lightweight, WebAssembly is an ideal technology for applications based on sandbox schemes. It has got noticed from communities of containers, function computing, IoT, and edge computing. What is WebAssembly? Is it capable of replacing Docker?
This article is based on the share by Michael Yuan, the maintainer of WasmEdge(project under CNCF now), in the 2020 KubeSphere Meetup.
Where WebAssembly Lies in Server
We tend to divide container, virtual machine, or operation environment into three different levels in terms of server.
The bottom lies Hypervisor VM of hardware, or AWS Firecrackers, which is known as microVMs with direct connection with the hardware.
The middle lies Application containers VM, where application containers such as Docker can be created. Notice: The application container is still within the operation system level, so the whole operation system should be fully included.
The upper lies high-level language VMs that starts from JVM. WebAssembly is abstracted from the level of the operating system. This is where WebAssembly lies in the server.
If WebAssembly manages to create a language VM similar to JVM, the dream proposed by Java over 20 years ago can be realized: to provide developers with a secure and highly abstracted operation environment across different operating systems, hardware, and software platforms.
Comparison between WebAssembly and Docker
What is the relationship between WebAssembly and Docker? Why is it believed that WebAssembly will replace Docker? Compared with Docker, WebAssembly performs better in the following aspects.
- In terms of cold start, WebAssembly is 100 times faster than Docker.
Slow cold start is a long haunting problem confronted by serverless and container service. As AWS provides reserve instances, keep it hot will offset advantages brought by serverless. Reserve will lead to charge by the day, which goes against the charge by millisecond we expect. One prominent edge of WebAssembly is no need to start the whole operating system, making it 100 times faster than Docker’scold start.
- In terms of execution duration, WebAssembly is 10% - 50% shorter than Docker.
WebAssembly is free from the operating system as a simple virtual machine, making its execution duration 10% - 50% shorter than that of Docker.
- WebAssembly occupies a smaller space.
The applications based on WebAssembly are generally within 1MB in size, while one Docker image can be 100 or 200 MB in size.
- WebAssembly embraces a modern security policy.
WebAssembly enjoys its “Capability-based Security” strategy, a risk control strategy based on resources offered. Different operating system interface/resources permission provided for each independent module instance can be designated by callers when instantiating each module.
- WebAssembly facilitates the combination of software.
- WebAssembly seamlessly supports server application frameworks, such as Node.js and Python.
These are where WebAssembly stands out.
WebAssembly and Rust
When it comes to WebAssembly, Rust always comes together. Crowned as the most popular language among developers in Stack Overflow, Rust is likely to replace C language in the foreseeable future.
As WebAssembly is connected with LLVM, 20 languages are supported at the front-end. C++ and Rust are highly supported, while Python, Java, and other programming languages with runtime are not well supported. That’s why we believe WebAssembly and Rust are perfect for each other, just like Java and JVM.
Rust improves development efficiency and security in memory. WebAssembly is conducive for secure operation and cross-platform execution. Both of them are of good performance and lightweight.
WebAssembly System Interface(WASI)
WASI is similar to JNI of Java. WebAssembly used to be applied in the browser and will be applied in the server-side this year. To access the file system, thread, order, and standard library in the server, WASI is indispensable.
Given one significant application scenario of serverless is AI reasoning, GPU, ASIC, and Tensorflow are highly required during the runtime of WebAssembly, which are all added by WASI.
Combining WebAssembly with Kubernetes
WebAssembly is frequently applied in browser, while seldom used in server, as it requires managing processes and allocating resources on its own due to the shortage of scheduling capacity and DevOps solution scheme in server-side. Hence, the combination of WebAssembly and Kubernetes makes an edge-cutting field.
One method is to make WebAssembly into OCI (open container interface) compliant. The other is to write shim API in containerd.
Now, you can use Docker tools like Docker Hub to manage WebAssembly images.
As we mentioned above, the tweet of Docker’s founder caused huge impacts on the community and led to some grudges. For ceasing these discontentment, another tweet was posted by him for an explanation. One and half years later, we found the reality different, and the word “Docker” should change into “Kubernetes”.
Will WebAssembly replace Docker
Even if WebAssembly can replace Docker, it takes time since Docker holds its ecology and is in a different abstraction level from WebAssembly.
However, WebAsembly will see extensive applications in some fields requiring high performance and lightweight, including micro-service, JAMStack, and edge computing.