ADN Frequently Asked Questions

The Application Delivery Network (ADN) platform specializes in improving data delivery performance for sites that deal with database-driven or user-specific content. For example, leveraging ADN to serve social media, online banking, and e-commerce sites will generate significant improvements in web page load times.

Yes. ADN was designed to speed up data delivery from any customer origin server.

Traditional CDN service achieves significant data delivery performance improvements through its caching technology. The strategy of caching content relies on many users within the same locale requesting static contentRepresents content that does not have to be modified or generated prior to delivery. For example, if an image is served from your storage server without modification, then that image is considered static content. to produce significant improvements in data delivery performance. Since dynamic contentRepresents content that is generated or modified upon being requested. An example of dynamic content is a web page generated by PHP. is unique and therefore the same response is not typically delivered multiple times, an alternative strategy must be used. This is where ADN comes into play.

In addition to leveraging our worldwide network, the following optimizations have been applied to our ADN service:

• Streamlined edge to origin server communication through ADN Gateway servers.
• RFC-compliant protocol optimizations.

• By default, caching has been disabled.

  Learn more.

It supports the following features:

• HTTPS
• Token-Based Authentication
• Country Filtering
• Rules Engine
• Analytics
• Web Application Firewall (WAF)
• Rate Limiting

The purpose of the ADN Gateway server is to ensure that requests are routed efficiently through our network to your origin server.

ADN Gateway servers assess their ability to communicate with the server(s) associated with a customer origin configuration by requesting the asset specified in the Validation Path option. The results of this query will generate a failover list of the top three ADN Gateway servers, in terms of performance, for the customer origin configuration that triggered this assessment.

This assessment is triggered by any of the following events:

• The creation of a customer origin configuration
• Reset is clicked when viewing or modifying a customer origin configuration

Each customer origin configuration is assigned a failover list of our top performing ADN Gateway servers. This failover list ensures that traffic to your origin server is routed over an optimal path in the unlikely case of ADN Gateway server failure.

An ADN Gateway server may be unavailable as a result of routine maintenance or an unplanned outage. If this occurs to an ADN Gateway server serving traffic for your customer origin configuration, traffic will automatically fail over to the next ADN Gateway server in that customer origin's failover list. Additionally, periodic checks will be performed to see whether the ADN Gateway server in question may resume serving traffic.

Yes. However, due to the dynamic nature of the content typically routed through ADN, caching is turned off by default on this platform. Caching on the ADN platform may be enabled through Rules Engine by disabling the Bypass Cache feature on the desired requests. Make sure that a cache policy is defined for the desired requests either by your web server or through Rules Engine.

Yes. However, purging is unnecessary unless caching has been enabled on the ADN platform.

• Content Delivery

  • ADN
  • IPv6
  • Cache Management
  • Rules Engine

• Security

  • CDN Security
  • MCC Security
  • Origin Shield
  • Token-Based Authentication
  • Web Application Firewall (WAF)

• Streaming

  • Dynamic Cloud Packaging
• Raw Logs
• Route (DNS)
• Storage