We performed a comparison between Chef and Nolio Release Automation based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation."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."
"The scalability of the product is quite nice."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"The most valuable feature is automation."
"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"Deployment has become quick and orchestration is now easy."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The CA Application Insight feature is the solution's most valuable aspect."
"One standout aspect is its architecture. We can configure multiple instances on a single server using different system names or usernames."
"The graphical view of when you're writing flow is the most valuable feature."
"Since we are heading to IoT, this product should consider anything related to this."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"In the future, Chef could develop a docker container or docker images."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Support and pricing for Chef could be improved."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"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."
"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."
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 "Useful for large infrastructure, reliable, but steep learning cureve". 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, Microsoft Configuration Manager and AWS CloudFormation, whereas Nolio Release Automation is most compared with GitLab, Red Hat Ansible Automation Platform, Microsoft Azure DevOps, UrbanCode Deploy and Automic Continuous Delivery Automation.
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.