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."It is a well thought out product which integrates well with what developers and customers are looking for."
"The product is useful for automating processes."
"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 important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"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."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"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."
"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 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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"Since we are heading to IoT, this product should consider anything related to this."
"It is an old technology."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"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."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"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."
"The configuration of the solution is a bit difficult to maneuver. They should work to make it easier."
"It could use better integration with development tools."
"When I started using Nolio around eight months ago, a challenge was the lack of relevant information and related support for learning."
"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 "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.