Edge Application

Edit on GitHub

Azion Edge Application allows you to build your web applications to run on Azion’s Edge Computing platform.

You can use the features such as Edge Caching, Application Acceleration, and Edge Functions to build more robust web applications, capable of meeting large access peaks with better performance and security for your users.

  1. How Does it Work?
  2. Edge Caching
  3. Minimum TLS Version
  4. Edge Application Modules
  5. Support Documentation

1. How Does it Work??

Azion works with a reverse proxy architecture, through which your users connect to the Edge Nodes of our highly distributed global network, which will be able to cache their content or even perform functions of their application, in addition to having a wide arsenal for optimization.

When a user requests content on the internet, their browser or application starts with DNS resolution to translate the requested domain to an IP address. When using Azion, you will set up the DNS for your web application to point to a generated address when creating a Domain at Azion.

Azion selects, through your SDN Router, the Edge Node closest to the user, reducing latency and increasing the speed of content transfer.

In this architecture, your content or web application needs to be made available from a origin, which can be one or more web servers in your infrastructure, a cloud service or one of Azion’s Origin Services.

2. Edge Caching

Azion’s highly distributed global network allows you to deliver your content much more efficiently. Content that is cached (cache hit) on Azion’s Edge Nodes can be delivered directly to your users, from the nearest Edge Node, without having to access the origin. In addition to increasing performance and scalability for your content, you can save on your origin infrastructure.

A cache miss occurs when a content is requested and it is not in cache. Azion minimizes the effect of cache miss, by maintaining a keepalive connection with the origin, whenever possible, avoiding the overhead of the TCP/IP handshake. Regardless of the volume of simultaneous requests made to Azion’s Edge Nodes, each Edge Node will search the content at the origin only once per cache miss, which substantially reduces the impact on your infrastructure.

3. Minimum TLS version

The TLS (Transport Layer Security) protocol allows you to encrypt web traffic. Currently the protocol offers some versions that can be used, such as: TLS 1.0 (Deprecated), 1.1 (Deprecated), 1.2 e 1.3.

You will be able to choose the minimum version of TLS that will be supported to encrypt the traffic.

Attention: when choosing recent versions of the protocol, be aware that some old devices or browsers will not be able to access the Edge Application.

To use the functionality, follow these steps:

  1. Access Real-Time Manager and click the menu Edge Services and select Edge Applications.
  2. Add or edit one Edge Application.
  3. To choose the minimum version of TLS it is necessary that the Delivery Protocol in the Main Settings tab is HTTP & HTTPS.
  4. Select the minimum version of the TLS protocol that will encrypt the traffic.
Minimum TLS Version functionality is available in the latest version of Edge Application (Version 3).

If the functionality isn't visible, you need to update the version of your Edge Application to enable this and numerous other features.

4. Edge Application Modules

Azion provides modules so that you can build high-performance, scalable and secure applications, with much more simplicity and free of operational tasks. Check the documentations of each product:

5. Support Documentation


Digital Certificates

Real-Time Purge

Rules Engine

Single Origin

Didn’t find what you were looking for? Open a support ticket.