nginx

NGINX Unit: A Modern App Server for Modern Apps As personal computers became ubiquitous in the early 1990s, there was a growing appetite to consume applications. At the time, it took on average three years to develop an app from initial conception to deployment in production. This has changed dramatically – Amazon deploys a new or updated application every 11.7 seconds and Nordstrom, a 120-year-old American luxury retailer, has increased its deployment frequency from twice per year to monthly. Bringing apps to market faster enables enterprises to stay ahead of the competition, achieve scale quickly, and increase revenues through digital channels. Developers take center stage in this new world but they are under pressure to develop and deploy new apps at a frightening velocity. That, in turn, puts pressure on infrastructure and operations (I&O) teams to provide a flexible, multi‑language environment in support [ more… ]

F5 and NGINX: Delivering Flexible, Secure, and Durable Applications from Code to Customer Businesses are always looking for the next competitive advantage. Customers have more choice than ever, and expect every interaction to look, feel, and function as seamlessly as the Facebook and Google apps they use every day. As enterprises race to build new applications and roll out capabilities to meet their customers’ demands, a distinct pattern has emerged, often called “shadow IT”. In a traditional IT architecture with monolithic applications, the infrastructure or network operations (NetOps) team usually controls app deployment, which is subject to strict compliance, governance, and security requirements. But DevOps teams in such environments – faced with both the internal pressure to innovate and the external pressure to bring services to market quickly – often circumvent such controls for the sake of agility. Even if [ more… ]

Introducing NGINX 1.16 and 1.17 Today we release NGINX 1.17.0 – the latest version of the NGINX open source project, which is now the most popular web server on the Internet. This release also signals the start of the NGINX 1.17 development branch, following the release of NGINX 1.16.0 last month. In this blog we discuss the NGINX versioning scheme, look back at what happened during the NGINX 1.15 development cycle, and look forward to what is in store with NGINX 1.17. NGINX Versioning Explained At NGINX, we maintain two branches in the NGINX source code repository, named mainline and stable: Mainline is the active development branch where the latest features and bug fixes get added. It is denoted by an odd number in the second part of the version number, for example 1.17.0. Stable receives fixes for high‑severity bugs, but is not updated with new features. [ more… ]