HashiCorp Nomad vs. Tidal by Redwood

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

On coming to well suited experience while error handling and effortless recovery processes are crucial, Tidal performs exceptionally well. It can identify and fix automated issues, reducing downtime and interruptions. A smaller automation solution may be more cost-effective if a business primarily utilizes a single platform or uses a small number of applications that do not require complex integration.

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

• Tidal Automation allows us to automate and schedule/ perform various tasks in a easy and effective manner. It is highly interactive and effective allowing nearly 4k -5k jobs to run a day.
• Tidal is designed to be easily shareable and collaborative allowing multiple users to work at a particular time making work effective.
• Tidal allows us to ensure that every event which is triggered is exactly when it's supposed to be regardless of other activities which are going as well.
• It is user-friendly to generate the reports required of a particular object and allows us to test the codes perfectly well before executing in live environment.

• 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

• Still a bit slow when navigating. If you close a job you have to wait a few seconds to open another one. Even when you made no changes.
• When viewing a job and make no changes, the "ok" button changes the last modified date as if you made a change. No big deal, but wastes time when troubleshooting a problem and looking into what jobs were changed last.
• You can see the parameters column in the "job activity", but not in "Job definitions".
• Can't search the parameters field in the filter.
• Changing a variable name does not change it on the job. It still works because Tidal Automation uses the ID number. It just causes confusion when you see a variable on a job and can't find the variable under "Variables". On top of that, Tidal Automation does not show the ID column under "Variables" making it even more difficult to find the variable.

We are on the fence. The increased pricing for renewals is staggering. With new automation options like Microsoft's Power Automate and Event Driven Ansible on the field, there are other options now available.

Having provided consulting services for years on Tidal by Redwood, I recommend going with a solutions partner or consultant to deploy it. I believe there are sizing and tuning guidelines that should be followed for environments of scale. I believe they are not critical when first lighting up the product, but if you are not aware of them you will encounter performance degradation after a few thousand job objects are added.

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

1. Tidal is good at processing large volume pf data and is cost effective. 2. Tidal can automate the scheduling of production objects, ensure that materials are delivered on time 3. Tidal Process large volumes of data which cannot be done everyday by running codes/scripts manually which does it with ease when required.

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

• Better decision-making and more process visibility are achieved through reporting and monitoring.
• Lowered time frames and streamlined administration of the workflow.
• Improved cost and resource allocation, especially in cloud contexts.
• A decrease in manual errors and related expenditures.
• Unusual problems that could occur during automation.
• Possible difficulties shifting to a new automation tool.
• The expense of beginning implementation and training.

Incentivized