1. Home
  2. Application Server Software
  3. NGINX Reviews
  4. User Review of NGINX
Nginx is best when used with a good dose of services and APIs
Updated May 17, 2021

Nginx is best when used with a good dose of services and APIs

Anatoly Geyfman | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with NGINX

We use NGINX as our web-facing server, behind which we have a collection of services serving various parts of our application. NGINX helps us map a single API over a variety of services, and make our API endpoints consistent across the various services. Nginx also helps with uptime, by helping us switch between various instances of the services in near real-time.
  • Extremely high-performing -- NGINX is never a bottleneck.
  • Easy to configure -- the configuration language is easy to learn, and allows very flexible scenarios.
  • Lightweight -- it's a very small service, which is never a memory or CPU hog.
  • Management tools -- Nginx has good errors, but it would be nice if it plugged into our cloud hosting infrastructure a little easier.
  • Configuration error detection -- for more complex configurations, sometimes Nginx isn't overly helpful when telling us what's wrong.
  • Lightweight, low CPU and memory utilization, meaning it's cheap to operate.
  • It's easy to configure and industry-standard, so lots of people know how to use it.
  • Helps model lots of scenarios where a more expensive or heavier-weight tool might have been used.
Nnginx is more light-weight than many other web servers, has a very expressive configuration language, easier to configure than tools like IIS and Apache, easy to install certificates for SSL, much easier to model complex routing scenarios than IIS, easier to configure than Apache. Overall, it's the leanest, best web server for services-oriented architectures (including microservices).
Ngnix is best suited as a public-facing proxy for everything that you might want to host. From WordPress to APIs, Ngnix does an extremely great job passing requests to those services, logging these requests in flexible ways, throttling requests when necessary, and even simplifying the downstream services by taking on some of the path extraction responsibilities (like extracting variables from paths and passing them in as headers).

It's not an application server, although they're working on it.