HashiCorp Nomad vs. NGINX vs. NGINX Ingress Controller

Nomad is well suited for organizations who wish to tackle the problem of cloud computing with as little opinion as possible. Where competing tools like Kubernetes limit the concept of "batteries included," Nomad relies on engineers understanding the missing components and filling them in as necessary. The benefit of Nomad is the ability to build a system out of small pieces with the cost of having more complexity at a system level compared to alternatives.

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

Best suited if we have to manage external traffic inside your Kubernetes cluster and want to use granular control to your applications.

Incentivized

• Nomad is incredibly simple by nature, following the Linux philosophy of doing one thing great. That one thing for Nomad is job scheduling.
• Nomad is a modern tool, written in Go with a large community and maintained by HashiCorp.
• Implementation of Nomad is very simple since it is a single binary.

Incentivized

• Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
• Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
• SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
• Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.

Incentivized

• Provide access to containers
• Manage traffic
• Route traffic
• Lightweight
• Near to zero downtime

Incentivized

• Nomad only handles one part of a full platform. Expertise and vision are required in implementing an entire system that is functional enough for an organization to rely on. This includes other tools to handle things like secrets, service discovery, network routing, etc.
• Nomad is delayed in some modern functionality, like features for service-mesh and open tracing. These features are on the tool's roadmap, but there's currently no native support. These paradigms can be established still, but require more expertise outside of Nomad itself.
• Nomad is not the leading tool for this space, and as such risks being left behind by tools with much greater support, such as Kubernetes.

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.

• Its not related to Ingress functionality but certificate management with cloud vendor would be a feature i would like to see.

Incentivized

Great value for the product

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

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

Nomad's primary competitor is Kubernetes, specifically its scheduling component. Kubernetes is a much more complete system that will handle more things than job scheduling, including service discovery, secrets management, and service routing. There also exists a much larger community support for Kubernetes vs Nomad. One might say Kubernetes is the safer choice between the two. Kubernetes is the complete "operating system" for cloud computing, but with it includes complexities that are "Kubernetes" specific. The decision really comes down to a mindset of monolith vs components. With Kubernetes, I would argue you choose the entire system as a whole. With Nomad, you design your system piece by piece. There is no wrong answer.

Incentivized

All of those are paid solutions with very good features, but they also offer dedicated scenarios for web application hosting. If you run applications on on-premises web servers and don't have a Microsoft licence agreement, Nginx is a very good and reliable option, based on Linux distributions and available as freeware.

Incentivized

We are already using NGINX which is so reliable, it definitely lends weight to our decision to select NGINX Ingress Controller. Also, even though it is a little more complex to manage, NGINX Ingress Controller definitely have a richer feature set, better performance, caching, traffic management among other features which was why it was chosen.

Incentivized

• Nomad has allowed our organization to deploy quicker and more frequently with a lower failure rate.
• Nomad has brought in consistency from an operations perspective.
• Nomad's performance allows us to scale infinitely while providing functionality that reduces mean time to repair (canary deploys, versioning, rollbacks, etc).

Incentivized

• Our websites are noticeably faster, causing an increase in customer satisfaction.
• Nginx has such a low memory/resource footprint that we save money from not needing multiple large, expensive servers.
• Ability to load balance traffic, have server-redundancy, and have high-availability allows for 100% uptime and provides cost-effective solutions to alternatives that can cost a lot.

Incentivized

• Security is one of the best objective which we achieve with NGINX Ingress
• Cost optimization is one of the business objective

Incentivized