NEWS

NGINX Unit 1.10.0 Is Now Available Summer’s gone, so it’s time to forfeit the halcyon tranquility and get some working attitude on. The NGINX Unit team has recently presented our first two‑digit version, NGINX Unit 1.10.0; let’s page through the recent developments and shed some light on our plans for the future. Routing Advancements In our two latest releases, some major effort went into extending the request routing capabilities that were initially introduced in NGINX Unit 1.8.0. Version 1.9.0 included essential support for arguments, headers, and cookies in matching clauses, whereas NGINX Unit 1.10.0 added scheme‑based routing to the mix. A few examples: “match”: { “host”: “www.example.com”, “arguments”: { “mode”: [“mobile”, “desktop”], “ui”: “!full” } } This condition matches queries like www.example.com/?mode=mobile and www.example.com/?mode=desktop&ui=compact, but not www.example/com/?mode=desktop&ui=full. “match”: { “headers”: [ { “Accept-Encoding”: “*gzip*”, “User-Agent”: “Mozilla/5.0*” }, { “User-Agent”: “curl*” } ] [ more… ]

Global Server Load Balancing with NS1 and NGINX Plus Global server load balancing (GSLB) is the practice of balancing load (connections or requests) across two or more distinct data centers or points of presence (PoPs). It is used to achieve several goals: Improving high availability (HA) – Route traffic away from a failed data center to operational ones. Reducing latency –Route each client to the data center that is closest to it. Improving performance by balancing load – Route connections to the data center that has the most capacity. Managing cost –Route traffic to the lowest‑cost data center. Most commonly used in a ‘cloud‑bursting’ scenario, when a higher‑cost data center is brought online only when its capacity is required. GSLB is generally implemented by managing the DNS resolution process; when a client makes a DNS lookup, it is given one or more IP addresses [ more… ]