Likelihood to Recommend 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.
Read full review As it is an open-source platform as a service, it is very easy to operate, scale, and deploy regardless of what programming language and framework it's written in. However, it could be improved in terms of scalability. There should be proper documentation for easier and clearer understanding to make the process smooth.
Read full review Pros 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. Read full review Simplicity - the command line tool provided can get you up and running within minutes. Resourceful - IBM Cloud Foundry is built on top of the open source Cloud Foundry technology, so any resources you find online about Cloud Foundry generally can be applied. Feature rich - provides all the necessary features for a cloud based platform, such as auto-scaling, 0 downtime deployment. Read full review Cons 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. Read full review Need: VISUALIZATION CAPABILITIES! Particularly with the Conversation Service. Need: Annotation capabilities for dialog nodes in Conversation Service. Need: Search/querying capabilities in Conversation Service Need: Clearer documentation of the S2T service. I had to use a third party website for an understanding of how to use this. River Hain Solution Analyst — Machine Assisted Service Enagagement
Read full review Alternatives Considered 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.
Read full review CF is what we initially went with to establish a development pipeline and start our cloud journey, now we are expanding this and although we are now pulling in many other tools and functions around CF, it is not being replaced. It stands out as having a key place working ‘with’ git,
Kubernetes , IBM cloud etc, not against or segregated from it.
Read full review Return on Investment 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). Read full review IBM Bluemix is mainly a foundation enabler at this stage, although our business plan does look promising. The low cost of development on Bluemix for a start-up like us is so helpful......we had no spare cash for this project besides what we could save or borrow at first, and that wasn't much. We are still trying to attract venture capital to cover the main Cordova Coding effort plus the launch "Cash Burn". Features like push notifications, mobile-back end, and world-beating security help us to sell our SaaS products/services. The pure (usually!) functionality of IBM products and services is very rewarding to work with.They are so insightful and thoughtful, to say naught of clever! Read full review ScreenShots