Our organization has a microservices architecture with different microservices based on business domains. We've been working on moving from a monolith to microservices for the last four years. People often ask why we don't use Kubernetes. One reason is that we have a mix of SaaS and on-premises solutions. We understood that the learning curve for Kubernetes would be higher for customers, and the investment for customer support for on-premises customers would be greater. HashiCorp Nomad is easier.
Has out of the box features , which is good for companies that don't want to spend too much time on research
What is our primary use case?
What is most valuable?
You could get most of HashiCorp Nomad's features from other microservice orchestrators like Kubernetes. The tool's advantage is its ease of use and integration with services like Envoy. With Kubernetes, you must think about many things, like UI integration, which vault to use, and how to discover the service. With the tool, many things come out of the box, making it easy to start. For example, using the Ingress proxy with the tool is quite easy, while it's trickier with Kubernetes.
What needs improvement?
I've noticed a few UI issues. For example, when monitoring services and tasks, sometimes the tasks keep disconnecting. If you open the shell in HashiCorp Nomad using the exit button, it often disconnects, and you have to log in again. Sometimes, when I check the logs in the UI for microservices tasks, I encounter an issue where the logs are not visible. However, if I log in again after some time, refresh the page, or check a different container, the logs usually appear. These logs are being generated, as I can see them being shipped to my LogView. I'm not sure if this is a product issue or something related to our deployment, but I've noticed it.
For how long have I used the solution?
I have been using the product for five years.
What do I think about the stability of the solution?
We haven't faced any major issues related to the infrastructure. I'd rate it eight or nine out of ten. The product runs quite smoothly without many issues from the tool's side.
What do I think about the scalability of the solution?
For scalability, I'd say HashiCorp Nomad is solving my use case. There are some bugs with monitoring, and we've faced issues where we had to reach out to the HashiCorp team, but not very frequently. Those issues have been resolved efficiently. It's easy to expand the product, which is one reason we use it.
How are customer service and support?
I haven't personally interacted with HashiCorp's technical support team.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
The main competitor for HashiCorp Nomad is Kubernetes. If I had to choose, I'd probably pick Kubernetes because of the community support and flexibility, even though I haven't faced any major problems with HashiCorp Nomad.
How was the initial setup?
We have written a control plane script, so we're not deploying the whole HashiCorp stack from scratch. We have our own HCL files, and they are not being deployed daily. No developers are deploying every day. An initial Python script and a Terraform script are written, which deploy our control plane using HashiCorp. Writing those initial scripts would have had some challenges, but as developers working on day-to-day microservices in our organization, we don't deploy from scratch.
What other advice do I have?
I'd recommend HashiCorp Nomad for medium-sized companies. For enterprise-scale, alternatives like Kubernetes have more community support. With HashiCorp Nomad, many things come out of the box, which is good for companies that don't want to spend too much time initially on research. I rate it an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
