Likelihood to Recommend
[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.
Read full review
API mocking, testing, and sharing are all built in functions for StopLight that work quite well. They even have functionality for generating OAI and RAML code as well, which is a huge plus. AS for as areas where StopLight is not appropriate, if you're doing anything other than API testing, StopLight may not be appropriate for use.
Read full review Pros Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture). Great at serving static content. Scales very well. Easy to host multiple Nginx servers to promote high availability. Open-Source (no cost)! Read full review OpenAPI support Markdown supports Git integration Read full review Cons Customer support can be strangely condescending, perhaps it's a language issue? I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this. It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work. It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together. I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments. Read full review Simplicity of set up. Although it's not difficult, there are tools out there that are easier to set up for testing endpoints. Again, it's perfectly functional, but some competitors I think have a more user friendly UI to them. Read full review Likelihood to Renew
Great value for the product
Read full review Usability Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also . Also, Nginx doesn't delay any request because of internal performance issues. from the administration perspective Read full review Support Rating
Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.
Read full review Alternatives Considered
We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
we have a large number of services and we can manage a single Nginx instance for all of them we have high impact services and Nginx never breaks a sweat under load individual services have special considerations and Nginx lets us configure each one uniquely Read full review
I'd like to also throw Runscope and Fiddler into the mix. Between StopLight and all these competitors, we've chosen StopLight primarily for the support, ease of use, and reliability. Most tools out there today are top-notch, so it really comes down to personal preference and different use-cases. Having used other API testing frameworks, StopLight definitely stacks up against the competition.
Read full review Return on Investment Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache. Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy"). Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly. Read full review Increased efficiency Improved comminication between backeend and frontend Read full review ScreenShots