We performed a comparison between Automic Continuous Delivery Automation and Chef based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation."It gives us good feedback on visualizations and on how our processes have progressed."
"The product provides efficiency, in terms time, cost, and resources."
"The main benefit is you can deploy everything with it."
"Gives people insight into what's happening during the deployment."
"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"I think on a day-to-day basis, it has increased the capacity to deploy. We don't have to wait for someone to do something."
"The IT process automation is the most valuable aspect of this solution."
"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."
"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."
"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."
"Deployment has become quick and orchestration is now easy."
"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 most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"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."
"It would be very beneficial for us to see integrations into cloud environments, especially into the Google Cloud environment because we are heading towards cloud."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"If you have a technical problem and need development of the tool, the support team is terrible, because they cannot help with the technical details."
"One of the biggest features I've been asked by my team to put in there is opening more scripting languages to be part of the platform. There is a little bit of a learning curve in learning how to code some of the workflows in Automic at this time. If widely used languages like Perl and Python were integrated, on top of what's already there, the proprietary language, it would make it easier to on-board new resources."
"key thing is support for cloud-based deployment. That is lacking."
"The stability of the solution can be improved."
"There is an issue with the stability in the tool. The process of agent will stop, then the monitoring agent can't be recognized because the process is running, but you can talk with the system."
"I would like to see more support for WebSphere."
"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."
"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."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"In the future, Chef could develop a docker container or docker images."
"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."
More Automic Continuous Delivery Automation Pricing and Cost Advice →
Earn 20 points
Automic Continuous Delivery Automation is ranked 17th in Release Automation while Chef is ranked 12th in Release Automation with 18 reviews. Automic Continuous Delivery Automation is rated 8.0, while Chef is rated 8.0. The top reviewer of Automic Continuous Delivery Automation writes "Reduces our time to market considerably with automated and consistent results". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". Automic Continuous Delivery Automation is most compared with UrbanCode Deploy, Nolio Release Automation and Microsoft Azure DevOps, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix.
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.
