Edge’s architecture creates a hyper-local peering system that routes traffic from nodes that are as close to the end consumer as possible – going as far as delivering within the local network loop.
This reduces the distance and volume of data being moved, which massively increases the performance of services.
Edge CDN has hundreds of nodes in over 80 countries, getting your content closer to your audience than ever before.
Edge Content Delivery includes a media pipeline that allows for just in time image manipulation: Blur, filter, flip, format, resize, rotate, saturate, sharpen and crop. This offsets the weight of media management to your delivery solution.
Real time compression and resizing of assets at the point of request saves an average of 60% in filesize, speeding up delivery, reducing your overall costs and increasing conversion.
Take workload off your origin by serving SSL certificates directly at the edge, accelerating performance and increasing availability.
Edge CDN saves 20%+ on average vs. traditional CDNs as a result of better media compression and the use of edge devices instead of centralised data centres.
You can launch a new instance of Edge CDN here: cdn.new
Documentation can be found here: edge.network/en/content-delivery/documentation
Edge content delivery can be seen running on Monocle.com, where it handles all media and asset delivery.
Checking the headers from an image call returns the cache state for the asset in the network, as well as the device IDs of the nodes involved in its delivery.
HTTP/1.0 200 OK =>Access-Control-Allow-Origin => *Cache-Control => public, max-age=86400Cdn-Version => 0.0.9Content-Length => 180462Content-Type => image/jpegDate => Tue, 23 Mar 2021 12:48:14 GMTEdge-Device => deb70d83-ca59-4345-adbc-da1ae06e76caEdge-Gateway => fb7fe194-9b46-4bcc-b7ae-e813dbc4d278Edge-Host => c41babfe-c9dd-43cb-aa1b-a5b31dc4d953Etag => "180462-b12ba916f5f133e321ee67706cb8ba29f1014f4adf0b90a0a234d2cbe4b60022"Strict-Transport-Security => max-age=10886400; includeSubDomainsVary => Accept-EncodingX-Cache => HITX-Cache-Origin => requestX-Cache-Type => mem