|
1 |
| -# About Hyper |
| 1 | +# About HyperContainer |
2 | 2 |
|
3 |
| -Hyper is a **Hypervisor-agnostic Docker Runtime** that allows you to run Docker images on any hypervisor (KVM, Xen, etc.). |
| 3 | +HyperContainer is a **Hypervisor-agnostic Docker Runtime** that allows you to run Docker images on any hypervisor (KVM, Xen, etc.). |
4 | 4 |
|
5 | 5 | Technically speaking,
|
6 | 6 |
|
7 |
| - Hyper = Hypervisor + Kernel + Docker Image |
| 7 | + HyperContainer = Hypervisor + Kernel + Docker Image |
8 | 8 |
|
9 |
| -By containing applications within separate VM instances and kernel spaces, Hyper is able to offer an excellent **Hardware-enforced Isolation**, which is much needed in multi-tenant environments. |
| 9 | +By containing applications within separate VM instances and kernel spaces, HyperContainer is able to offer an excellent **Hardware-enforced Isolation**, which is much needed in multi-tenant environments. |
10 | 10 |
|
11 |
| -Hyper also promises **Immutable Infrastructure** by eliminating the middle layer of Guest OS, along with the hassle to configure and manage them. |
| 11 | +HyperContainer also promises **Immutable Infrastructure** by eliminating the middle layer of Guest OS, along with the hassle to configure and manage them. |
12 | 12 |
|
13 |
| - |
| 13 | + |
14 | 14 |
|
15 |
| -Performance-wise, **Hyper is super light**: |
| 15 | +Performance-wise, **HyperContainer is super light**: |
16 | 16 |
|
17 |
| -- **Sub-second Boot**: milliseconds to launch a HyperVM instance |
| 17 | +- **Sub-second Boot**: milliseconds to launch a HyperContainer |
18 | 18 | - **Slimmed Footprint**: ~28 MB RAM (512MB on AWS EC2)
|
19 | 19 |
|
20 |
| -With Hyper, the future of Container-as-a-Service is just around the corner. |
| 20 | +With HyperContainer, the future of Container-as-a-Service is just around the corner. |
21 | 21 |
|
22 | 22 | 
|
23 | 23 |
|
0 commit comments