Edge Application

Edge Application is an Azion product that allows you to build applications that run in Azion’s edge network. By reducing latency and enhancing throughput, Edge Application optimizes your end-user experience by bringing your application closer to them.

By operating on a reverse proxy architecture, Edge Application allows you to create applications on the edge and direct traffic from your domain to Azion. Through this process, your users can effortlessly access your application via a highly distributed global network of edge nodes. Then, Azion selects which edge node closest to the user can handle the request.

Your content or application has to be available from one or several origins. This origin can consist of one or more web servers from your infrastructure, a cloud service, or one of Azion’s Origin services.

With Edge Application, you can:

  • Define how your content will be cached.
  • Execute functions at the edge.
  • Bring your business rules for any request or response.
  • Optimize content and image delivery for your users.
  • Customize origins and error pages.
Build your first edge application

You can create and manage edge applications using:

ScopeResource
Edge Application first stepsFirst steps
Clone an edge applicationHow to clone an edge application
Delete an edge applicationHow to delete an edge application

Modules can complement your implementation of Edge Application. You can enable or disable modules in the Main Settings tab of your application, provided your account supports them and there are no existing dependencies upon deactivation.

See the documentation for each module:

ModuleDescription
Application AccelerationOptimize API protocols and manage dynamic content delivery to accelerate applications and APIs.
Edge CachingConfigure cache settings to speed up the delivery of static and dynamic content.
Edge FunctionsBuild ultra-low latency applications and customize content delivery.
Image ProcessorOptimize image processing for various devices, browsers, and screen resolutions.
Load BalancerBalance traffic between your origin servers and cloud providers to improve fault tolerance and avoid network congestion.
L2 CachingCreate a new cache layer between your users and the edge to keep objects in cache for longer periods of time.
WebSocket ProxyEnable the WebSocket protocol to establish full-duplex communication channels over one TCP connection.

Edge Application allows advanced configuration of origins, cache, functions, error pages, and more, optimizing content delivery for improved performance and user experience.

See the documentation for each available setting:

SettingDescription
Main SettingsCustomize your application delivery with Azion’s range of protocol options including HTTP, HTTPS, and HTTP/3 support for a better user experience and secure your connection with TLS ciphers.
OriginsModify your origin address, Host header, path, protocol policies, and HMAC authentication credentials.
Device GroupsCreate groups to change your application’s cache and delivery behavior according to end-user devices.
Error ResponsesCustomize error response pages, their cache expiration time, and their origin.
Cache SettingsConfigure your application’s browser and edge cache expiration time, large file slicing, and advanced cache behavior based on cookies or query strings.
FunctionsInstantiate functions created with Edge Functions.
Rules EngineAutomate the execution of behaviors based on specific parameters for your edge application.

Azion Domains provides you with the flexibility to use automatically generated domains or your own custom domains, allowing you to manage and deliver content effectively through your edge applications with support for secure connections over HTTP and HTTPS.

Learn more about Domains

With Digital Certificates, you can enhance the security of your HTTPS applications by binding a custom TLS certificate to your edge application.

Learn more about Digital Certificates

Use Real-Time Purge to clear cached content from Azion’s edge or from the Layer 2 to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your edge application.

Learn more about Real-Time Purge

Azion enforces a keepalive connection duration limit of 10 to 15 minutes between users and edge applications. To avoid the termination of active connections that require more time to complete, consider implementing file slicing or file compression for large files to improve data transfer speeds.

These are the default limits for each Service Plan:

DeveloperBusinessEnterpriseMission Critical
1001001001,000

Contributors