Likelihood to Recommend
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
Read full review
[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 Pros Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions. Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy. Very good documentation and blog with details of most common failures and error handling. A very very easy to use console. Read full review 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 Cons Only one user can be active in a proxy at a time No version control Prohibited from using JSON.stringify on Apigee objects (tokens) Debugging is difficult Unable to rename or delete policies without bumping revision Why would anyone give a js policy one name, display name something else, and script a different name? 'Trace' limited to only 20 transactions UI allows users to add target servers, but users must utilize the api to turn on SSL. I'm sure there's more, they just aren't coming to mind right now. Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in. Read full review 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 Likelihood to Renew
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
Read full review
Great value for the product
Read full review Usability
Support has helped us to resolved all the queries and community support was also good.
Read full review 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
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
Read full review
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
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
Read full review
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 Return on Investment As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter. Read full review 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 ScreenShots