AWS announces CloudFront Functions

AWS Logo
AWS Logo

AWS announced general availability of “CloudFront Functions“. The product allows deploying lightweight functions on the edge of CloudFront’s CDN deployment, bringing logic close to the end user. After CloudFlare initiated a trend with their Workers, AWS is the third major cloud player to enter the space with this offering.

The purpose of such an architecture is to bring specific logic closer to the consumer, therefore delivering richer, more personalized content with lower latency. With a distribution across 225+ CloudFront edge locations in 90 cities across 47 countries the promise is huge.

To get developers kickstarted, AWS published a Github repo with examples. As one would expect, these are primarily revolving around http header manipulation and authentication. CloudFront Functions runs JavaScript.

Amazon CloudFront launches new Edge Locations
AWS Logo

Amazon CloudFront Edge Locations: AWS’ Amazon CloudFront launches 5 new CloudFront Edge Locations. These are located in Bulgaria, Greece, Hungary, Kenya, and Romania.

AWS CloudFront is a Content Delivery Network and helps webpages to distribute their content globally. To achieve this, CDN’s leverage managed reverse proxy servers. The goal is to bring content closer to the consumer. And through keeping bulky media distributed, it prevents congesting internet connections.

These added deployments will help AWS customers and their consumers experience significantly improved page load times. AWS has constantly expanded CloudFront’s Network footprint since its launch in 2008. With this recent update, CloudFront now has 216 points of presence in 84 cities across 42 countries. 

Source: aws blog.

AWS CloudFront Monitoring Update: AWS released an early & small Christmas Gift to their CloudFront Customers. CloudFront now supports eight more metrics to monitor content distribution. These include:

Cache Hit Rate via HTTP POST and PUT requests, via the percentage of all cacheable requests for which CloudFront served the content from its cache, including errors not considered cacheable requests.

Origin Latency as a quota and the total time spent for requests that are served from the origin, not the CloudFront cache. Origin Latency allows to monitor the performance of your origin server.

Error Rate by status code as a percentage of requests for which the response’s HTTP status code is in the 4/5xx range, in particular 401, 403, 404, 502, 503, and 504.

AWS CloudFront Monitoring Update via AWS Blog.

On Latency

Andrew Certain helps getting an understanding of percentile measurements and why it is important to look at certain things from specific perspectives. I found this useful.

SPDY und HTTP im Vergleich

Guy Podjarny, Chief Product Architect bei Akamai Technologies, hat sich die Mühe gemacht SPDY in der wahren Welt zu evaluieren. Obwohl SPDY einige sinnvolle Ansätze verfolgt, scheinen die absoluten Erbenisse eher überschaubar zu sein. Die Ergebnisse seiner Untersuchungen hat Guy in seinem Blog “Guy’s Pod” zusammengefasst.