We performed a comparison between Chef and Nolio Release Automation based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Manual deployments came to a halt completely. Server provisioning became lightning fast. Chef-docker enabled us to have fewer sets of source code for different purposes. Configuration management was a breeze and all the servers were as good as immutable servers."
"The most valuable feature is automation."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"Chef recipes are easy to write and move across different servers and environments."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The most valuable feature is the language that it uses: Ruby."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"The graphical view of when you're writing flow is the most valuable feature."
"One standout aspect is its architecture. We can configure multiple instances on a single server using different system names or usernames."
"The CA Application Insight feature is the solution's most valuable aspect."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"It is an old technology."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"Support and pricing for Chef could be improved."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"The configuration of the solution is a bit difficult to maneuver. They should work to make it easier."
"A concern with CA Release Automation is that Automic was acquired by CA recently. We're a bit concerned that CA strategy is going with Automic, that CA Release Automation is dead. They are not investing in it too much... They do say, that in the next two or three years we don't need to worry. They will still provide support for CA Release Automation. But we're not sure how CA Release Automation will evolve."
"In the next release, I would like to see more features to use active directory. And more rules to support more Python scripts and to work with Kubernetes and clouds, to have an easy solution for a lot of parameters."
"When I started using Nolio around eight months ago, a challenge was the lack of relevant information and related support for learning."
"It could use better integration with development tools."
Chef is ranked 15th in Release Automation with 18 reviews while Nolio Release Automation is ranked 12th in Release Automation with 50 reviews. Chef is rated 8.0, while Nolio Release Automation is rated 7.8. The top reviewer of Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". On the other hand, the top reviewer of Nolio Release Automation writes " Enables one-touch application deployment across various environments". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, BigFix and Red Hat Ansible Automation Platform, whereas Nolio Release Automation is most compared with GitLab, Red Hat Ansible Automation Platform, Microsoft Azure DevOps and UrbanCode Deploy. See our Chef vs. Nolio Release Automation report.
See our list of best Release Automation vendors.
We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.