Ambassador Cloud vs. NGINX

Ambassador is really well suited for scenarios were you need to give power and freedom to your developers so they can take advantage of the self-service approach. One of the few scenarios I can not recommend using Ambassador is in the case you are planning to not using Kubernetes as it is a solution designed to work specifically on that platform

Incentivized

[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.

Incentivized

• Simple syntax
• Easy to understand
• Easy to install

Incentivized

• 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)!

Incentivized

• Documentation is not updated
• Implementing external authentication doesn't always work as described in the documentation
• The Administration console is limited

Incentivized

• 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.

Great value for the product

Incentivized

It's great! it's amazingly simple to use and the best part is the self-service approach. I also like how easy it is to add a new route to a endpoint with the mappings definition.

Incentivized

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 from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.

Incentivized

Overall the support has been great and quick to answer the requests I've submitted in the past. I was originally using the community/open source version and I can't say it was the best experience I had, it wasn't terrible but it wasn't great. I believe the biggest issue was that they refer to the documentation a lot but the documentation isn't updated regularly so I feel it's lagging behind the most recent versions.

Incentivized

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.

Incentivized

They both offer about the same in terms of end goal and purpose of use and scenarios. However, Ambassador does way better in terms of simplifying the syntax and makes offer a little bit more of control by adding the concepts of hosts, mappings while staying away from a hard to read single file configuration.

Incentivized

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

Incentivized

• Reduced downtime by redirecting traffic between DC.
• Reduced engineering time, don't have to dedicate 1 person to manage it.
• Increased training costs in the short term.

Incentivized

• 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.

Incentivized