Blackbird API Development 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 well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.

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

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

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

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

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

• By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
• Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
• Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.

Incentivized