Edge Container is a serverless compute service that runs container applications on a global network of points of presence (POPs). By deploying your applications closer to your users, Edge Container significantly reduces latency and simplifies protocol handling. It automatically manages scaling and operations, so you can focus on developing your application instead of managing infrastructure.
Benefits
-
Global deployment with low-latency access: You are no longer limited to deploying containers in a single region. Edge Container runs on points of presence (POPs) across the globe. Client requests are automatically routed to the nearest POP, which triggers your application, processes the request, and returns the result. Compared to centralized deployments, this model significantly reduces request response times for a low-latency compute experience.
-
ESA integration for powerful proxy and protocol offload: By leveraging the powerful protocol offload capabilities of Edge Security Acceleration (ESA), your container applications require no extra development for access protocols. Edge Container supports the ingress and offload of protocols like HTTP/3, HTTP/2, and TLS, allowing your business to easily benefit from the performance and security improvements of protocol upgrades. Edge Container also supports most ESA request and response handling features, such as request header modification and response compression.
-
Serverless, elastic, and easy to operate: You do not need to manage underlying infrastructure such as CPUs, memory, networks, or operating systems. You can focus on developing your code while Edge Container automatically handles container scaling based on your resource usage. It also rapidly detects and removes unhealthy containers, whether due to internal application errors or carrier network issues, to ensure high availability.
Core concepts
-
application: An application is the basic unit for managing Edge Container. Within an application, you can create and release multiple versions. You can also bind an ESA domain to an application for public access.
-
release: The release process begins with creating a version. You can configure different settings for each version, such as the image, compute specifications, and health check probes. Each version supports a maximum of one image. Edge Container supports a canary release, allowing you to control the traffic percentage during deployment. You can release a new version only after the current one handles 100% of the traffic. However, you can perform a rollback at any time.
-
trigger: A trigger invokes an Edge Container application. The domain binding feature allows you to connect a container application to your own domain. After binding the domain, you can use it to access the application directly. The domain must belong to an available site. Once configured in the console, ESA automatically adds a DNS record for the bound domain to the site's DNS configuration.
Feature availability by plan
|
Entrance |
Pro |
Premium |
Enterprise |
|
|
|
|
|