nginx

The following is adapted from a presentation given by Owen Garrett at nginx.conf 2015, held in San Francisco in September. You can view the video of the talk here. Table of Contents 0:00 Introduction 0:30 Massive Pace of Development in 2015 3:55 Why the Top Sites Choose NGINX 4:58 Building a Great Application… 12:30 nginScript 13:30 Announcing Dynamic Modules 18:00 NGINX Amplify 0:00 Introduction 2015 has been a really, really big year for NGINX. As Gus said in his keynote presentation, the company has grown, our user base has grown, and the number of customers using our software, taking advantage of our services continues to grow. But what I want to talk to you more about is how the product has changed. 0:30 Massive Pace of Development in 2015 Many of you track us on Mercurial, our source control system. [ more… ]

table.blog { border-collapse: collapse; } table.blog td { border: 1px solid black; padding: 5px; } In the previous article in this caching series, we looked at the benefits of microcaching – caching dynamic content for very short periods of time – which sometimes leads to very significant performance improvement. In this article, we’ll consider another aspect of caching, that of cache placement, and we’ll look at strategies for dealing with slow cache storage. Selecting a Cache Location NGINX can manage multiple cache locations, each mapped to a different filesystem location, and you can configure NGINX to choose which cache to use on a per-request basis. In the following sample configuration, the proxy_cache_path directives create two caches, ssd_cache and disk_cache, mounted on the local directories /mnt/ssd/cache and /mnt/disk/cache respectively. The map directive inspects the request URL and selects disk_cache for all requests that appear to [ more… ]

When correctly deployed, caching is one of the quickest ways to accelerate web content. Not only does caching place content closer to the end user (thus reducing latency), it also reduces the number of requests to the upstream origin server, resulting in greater capacity and lower bandwidth costs. The availability of globally-distributed cloud platforms like AWS and DNS-based global load balancing systems such as Route53 make it possible to create your own global content delivery network (CDN). In this article, we’ll look at how NGINX can cache and deliver traffic that is accessed using byte-range requests. A common use case is HTML5 MP4 video, where requests use byte ranges to implement trick-play (skip and seek) video. Our goal is to implement a caching solution for video delivery that minimizes user latency and upstream network traffic. Our Test Framework We need [ more… ]