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."It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed."
"The most valuable feature is automation."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"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."
"The graphical view of when you're writing flow is the most valuable feature."
"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."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Since we are heading to IoT, this product should consider anything related to this."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"In the future, Chef could develop a docker container or docker images."
"The agent on the server sometimes acts finicky."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"The configuration of the solution is a bit difficult to maneuver. They should work to make it easier."
"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."
"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."
Chef is ranked 12th in Release Automation with 18 reviews while Nolio Release Automation is ranked 13th 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 UrbanCode Deploy, 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.
