All Products
Search
Document Center

Benefits

Last Updated: Nov 29, 2021

Elastic Container Instance provides an O&M-free, elastic, cost-effective, and efficient container runtime environment.

Core benefits

The following list describes the core benefits of Elastic Container Instance:

  • Zero O&M

    Elastic Container Instance uses a serverless architecture and hosted infrastructure. You need only to provide container images to use Elastic Container Instance. You do not need to manage underlying servers, create and maintain clusters, or plan resource capacities. This helps you focus on the development of your business.

  • Flexible deployment

    Elastic Container Instance uses the global computing infrastructure of Alibaba Cloud as a resource pool to provide nearly unlimited computing resources of various types. The resources include CPUs, vGPUs, and resources with high clock speeds. All these resources support a large number of concurrent workloads, and are available to you at any time based on your business requirements.

  • Cost-effectiveness

    Elastic Container Instance are billed based on the resources consumed and the number of seconds from the start time to the stop time of the elastic container instances. If Elastic Container Instance is used together with Kubernetes or a user-created scheduling system, Elastic Container Instance can provide the auto scaling feature based on business traffic to reduce costs that are caused by idle resources.

  • High elasticity

    Elastic Container Instance supports instance startup within seconds and allows you to scale out resources on demand to cope with bursts in traffic of up to hundreds of times. You do not need to plan for your cluster capacity and business traffic.

  • Compatibility

    Elastic Container Instance is compatible with Kubernetes. You can directly schedule pods on Kubernetes clusters to elastic container instances. Elastic Container Instance is integrated with Container Service for Kubernetes (ACK) and serverless Kubernetes (ASK). You can also use Virtual Kubelet to connect an elastic container instance to a Kubernetes cluster that you built on Elastic Compute Service (ECS) or in an on-premises environment.

  • Integration

    Elastic Container Instance is automatically integrated with other Alibaba Cloud services to support features such as network access, log collection, data persistence, and service monitoring. These Alibaba Cloud services include Log Service, Apsara File Storage NAS (NAS), and Application Real-Time Monitoring Service (ARMS).

Comparison

A container group is the basic execution unit of an elastic container instance. Container groups in elastic container instances are fully compatible with Kubernetes pods. You can use an elastic container instance as the container runtime environment to improve the elasticity and security of your business system and reduce usage and O&M costs.

The following table compares the runtime environments provided by different container services of Alibaba Cloud.

Item

Elastic Container Instance

ECS

ECS Bare Metal Instance

Billable item

Only pods.

ECS instance.

ECS Bare Metal Instance.

O&M

Convenient O&M and lower costs without the need to manage nodes.

Node management and resource O&M required.

Node management and resource O&M required.

Performance

Low virtualization loss and instance startup within seconds without the need to reserve resources.

Low virtualization loss.

No virtualization loss.

Elasticity

Highest elasticity. Elastic Container Instance provides instances with lower specifications and higher inventory.

High elasticity.

Modest elasticity.

Security

Strong isolation between instances and strong isolation between pods.

Strong isolation between instances and weak isolation between pods.

Strong isolation between instances and weak isolation between pods.

Chance of failure

Extremely low. Failures are limited to individual pods and your business is not affected.

Extremely low. A single instance including pods deployed on the instance is affected.

Extremely low. A single instance including pods deployed on the instance is affected.