NEWS

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… ]

The following is adapted from a talk given by NGINX CEO Gus Robertson at nginx.conf 2015, held in San Francisco in September. Watch a video of the talk here. Table of Contents 0:00 Introduction 1:04 NGINX – Powering the World’s Busiest Websites 2:10 Where We’re Heading 4:36 Extraordinary Things 6:00 Changing the World 8:22 Flawless Application Delivery 0:00 Introduction Welcome to the second annual NGINX User Conference. My name is Gus Robertson. I’m the CEO of NGINX and I’ve been in open source now for well over a decade. I’ve been with NGINX for around three years, and I’ve seen some amazing milestones in those three years that I wanted to share with you this morning. 1:04 NGINX – Powering the World’s Busiest Websites Back in 2013, we became the number one web server for the 1,000 busiest websites in [ more… ]

Getting identity management right in modern application and API development is an increasingly important and demanding challenge. A number of developments in the industry are putting pressure on existing identity solutions. Integrated web experiences enable users to navigate seamlessly between different applications without requiring multiple login events. User experience is improved by giving users a choice about which identity they use with a given application, instead of requiring yet another password in yet another isolated, proprietary database. Microservices architectures (and decomposed monoliths) can require developers to reimplement the same authentication and authorization logic over and over. Applications deployed at scale (in a cluster) need to offload as many non-core operations as possible, for example encryption and authentication. Supporting the numerous existing identity standards involves undifferentiated heavy lifting that impinges on time spent on the application itself. At NGINX we are [ more… ]