Guest blogger Brian Gleason advises #NetOps managers on a couple ways to get the most from, and for, their greatest asset: their people. First, make sure they have time for focus on their own priorities. Second, learn enough about network technologies to communicate well.
The modern market’s demand for speed has heightened the tension between DevOps and NetOps/SecOps teams. But you can have both developer productivity and infrastructure reliability — bridge the divide with self-service app delivery tools from NGINX.
Guest blogger Jeremy Schulman explains for network engineers (or anyone!) how to get started with an API. He outlines the different types of documentation and their pros and cons, how to take advantage of client libraries, and the ins-and-outs of authentication.
We compare the reverse proxying performance of HAProxy and NGINX. Performance is similar until the request rate is large enough for HAProxy to hit 100% CPU utilization. At that point, its performance degrades significantly while NGINX continues to experience almost no latency.
Since our last update, the NGINX Unit team has released three versions, 1.19.0 through 1.21.0. New features include support for ASGI with Python, multi-threading with several languages (Java, Perl, Python, Ruby), regular expressions in routing conditions, and more.
We present the four winners of the 2020 NGINX Hackathon for Good, who each created an app to help people affected by a social issue, using NGINX Open Source and NGINX Unit. The winning apps address unemployment, social justice volunteerism, and transparency around charitable giving.
We feature answers from our experts to three key questions about NGINX automation asked at the panel discussion we held during AnsibleFest 2020: how official roles and collections add value, how to choose which tasks to automate, and why community input is so important.
Guest blogger Jason Benedicic describes several use cases from his daily life where real-time API performance is key to a satisfactory interaction with the app: his favorite dinner-delivery service, his home office with automated controls for lighting and connectivity, and his online-only bank.
Release 1.9.0 of the NGINX Ingress Controller introduces updated NGINX App Protect features, new policies (JWT validation, rate limiting, and mTLS authentication), improved visibility with new metrics and Grafana dashboards, integration with NGINX Service Mesh, and more.
We explain why traditional API management frameworks don’t work in modern, microservices-based app environments. The NGINX API management solution embodies features our customers tell us they need now: decoupled data and control planes, multi-cloud support, and self-service.
Guest blogger Jeremy Schulman offers practical advice for network engineers charged with increasing automation. First, focus on tasks that reduce operational friction among teams. Become familiar with the tools used by various teams, and learn how to use their APIs.
As a network engineer, there are everyday hurdles you face, from outages to design to performance problems. Now you must learn API, too? How do you start understanding the new world? Guest blogger and network engineer Brian Gleason provides guidance on how go about it.
Guest blogger and musician Caleb Dolister discusses an unexpected consequence of the COVID-19 pandemic: how hard it is to play music together remotely. Turns out the variable latency introduced by networks makes it nearly impossible to keep everyone on the beat.
We walk through a bash script for setting up a WordPress deployment on Ubuntu that’s managed by NGINX Unit and uses NGINX for web serving. The resulting WordPress deployment is scriptable, supports Let’s Encrypt, and has production-ready settings.
Application security is hard, but there are some best practices to help you achieve it: automate as much as possible, build security as a guardrail instead of a gate, select solutions that provide easily understood insights, and make security adaptable, scalable, and reliable.
We explore two use cases for filesystem isolation in NGINX Unit. First, we stop attackers from accessing sensitive information, by restricting a compromised app to its sandbox directory. Second, we toggle between sets of global dependencies by defining them in separate filesystems.
NGINX Unit 1.18.0 introduces filesystem isolation, the ‘target’ option to reduce redundancy in PHP app configuration, and URL encoding. It also includes features introduced in NGINX Unit 1.17.0: redirects, and fractional server weights for traffic distribution in upstream groups.
We announce the technology preview of NGINX support for QUIC+HTTP/3 as pre-release software, available for interoperability testing, feedback, and code contributions. HTTP/3 replaces TCP with QUIC, which is designed to support multiplexed connections more reliably.