nginx

Keeping NGINX Focused on Technology, Culture, and Customers Today we announced that NGINX has raised $43M in Series C funding. The round was led by Goldman Sachs, with contribution from our long-time investor, NEA. Total funding for NGINX is now $103M. With this round we also welcome David Campbell, Managing Director of Goldman Sachs’ Merchant Banking Division, to our board. I couldn’t be more excited to have David lend his guidance and perspective. But don’t take my word for it! Watch this short video to hear David explain his background as an IT leader and why he believes in the NGINX opportunity. Listening to David got me thinking, and reflecting on my five and a half year journey at NGINX. We have the largest VC in Silicon Valley and the most prominent investment bank on Wall Street as our anchor [ more… ]

NGINX Unit 1.2 Available Now On June 7 we released NGINX Unit 1.2, the latest version of our dynamic multilingual application and web server, with support for many exciting features that enable its use in more sophisticated environments. This follows the general availability (GA) release of version 1.0 on April 12 and the release of version 1.1, with bug fixes and minor updates, just a couple weeks later. NGINX Unit 1.2 includes these new features: All types of applications can now be dynamically configured with their own environment variables. Configuration options for PHP applications can be defined in the php.ini file or directly with the NGINX Unit API. Go executables can now be configured with command‑line arguments. These new features make your applications even more configurable. All parameters can be defined dynamically, without any disruption to running services or loss of connectivity. Let’s review [ more… ]

Deploying NGINX Plus as an API Gateway, Part 2: Protecting Backend Services This is the second blog post in our series on deploying NGINX Plus as an API gateway. Part 1 provides detailed configuration instructions for several use cases. This blog post extends those use cases and looks at a range of safeguards that can be applied to protect and secure backend API services in production. Rate Limiting Unlike browser-based clients, individual API clients are able to place huge loads on your APIs, even to the extent of consuming so much of the system resources that other API clients are effectively locked out. Not only malicious clients pose this threat: a misbehaving or buggy API client might enter a loop that overwhelms the backend. To protect against this, we apply a rate limit to ensure fair use by each client and to [ more… ]