rkt vs ZeroVM: What are the differences?
Developers describe rkt as "App Container runtime". Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast. On the other hand, ZeroVM is detailed as "Open-source lightweight virtualization platform". ZeroVM is an open source virtualization technology that is based on the Chromium Native Client (NaCl) project. ZeroVM creates a secure and isolated execution environment which can run a single thread or application. ZeroVM is designed to be lightweight, portable, and can easily be embedded inside of existing storage systems.
rkt and ZeroVM can be categorized as "Virtual Machine Platforms & Containers" tools.
Some of the features offered by rkt are:
- Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable.
- Security. Isolation should be pluggable, and the crypto primitives for strong trust, image auditing and application identity should exist from day one.
- Image distribution. Discovery of container images should be simple and facilitate a federated namespace, and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.
On the other hand, ZeroVM provides the following key features:
- Small, Light, Fast - ZeroVM is extremely small, lightweight, and fast. An execution environment can start in as little as 5 milliseconds.
- Secure - ZeroVM security is derived from the Chromium Native Client (NaCl) project and is based on the concept of software fault isolation.
- Hyper-Scalable - ZeroVM makes it easy to create large clusters of instances, aggregating the compute power of many individual physical servers into a single execution environment.
rkt and ZeroVM are both open source tools. rkt with 8.7K GitHub stars and 832 forks on GitHub appears to be more popular than ZeroVM with 738 GitHub stars and 71 GitHub forks.