Content Delivery Network
F5 Distributed Cloud Content Delivery Network (CDN) is a geographically distributed set of highly efficient servers that cache and deliver static and dynamic content. The CDN servers are positioned close to end users, and work in concert to optimize delivery to end users.
CDN traffic is globally distributed to all Sites with a CDN Distribution. The CDN Control Plane routes end user requests to a geographically proximate and healthy node.
Support for TLS authentication with policy-based authorization on the CDN Distribution enforces end-to-end security of application traffic.
Origin health is constantly monitored to ensure optimal uptime.
Introduction to CDN
With Distributed Cloud CDN, you have the ability to leverage the Distributed Cloud network to distribute static and dynamic content.
A cache miss occurs when a client device makes a request to the CDN and the CDN cache does not have the requested content.
A cache hit occurs when the CDN cache has the requested content.
Content is delivered with lower Time-To-First-Byte (TTFB) on a cache hit because the CDN can immediately deliver the content to the end user without having to make an origin pull.
An origin pull occurs anytime the CDN server needs to pass a request to the origin server. This typically occurs on a cache miss. On an origin pull, the CDN will cache the content contained in the origin server's response.
Subsequent requests for the same content will result in a cache hit and lower latency for end users.
Static and Dynamic Caching to Reduce Latency
End to End Security
Distributed Cloud CDN supports multiple delivery and origin security capabilities. Support for TLS is available from Client to CDN as well as from CDN to Origin.
Domains TLS certificate can be securely hosted with F5 Distributed Cloud’s unique solution called Blindfold and/or integration to external secrets management solutions such as Hashicorp Vault.
Global Load Balancing
Global Scale – Optimum DNS-based request routing across global Geo-distributed Data-plane
Geo-based Load-balancing – Matching clients to the closest available edge nodes based on Geo proximity
Resource-based Load-balancing – Matching clients to available edge nodes based on edge node resource consumption policies on network, CPU and storage utilization