We performed a comparison between Automic Continuous Delivery Director and Chef based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Microsoft, Red Hat and others in Release Automation."The most valuable features of Automic Continuous Delivery Director are the UI, release planning, and tracking, and you can do your soft and hard freeze through CDP."
"CDD is primarily used for showing end users (managers, business teams, project managers, and release managers) what is happening with each release. The status and reporting features are very important. Automation reduces time to deploy. It also allows us to do more with releases and testing prior to production, better guaranteeing a smooth deployment."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"The most valuable feature for me is the fact that you can easily design a pipeline to promote applications from a development environment up to a production environment, and the team can become autonomous in designing those pipelines."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"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."
"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."
"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 automation."
"The most valuable feature is the language that it uses: Ruby."
"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."
"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."
"We would like to have a more user-friendly interface. It is already very friendly, but as soon as you start to have many applications with many tasks, the applications should be easier to manipulate on the screen."
"Reporting and dashboarding could be improved. Release pipelines should be creatable via templates as well as easily integrable/chained together. Visual navigation could also be improved when the pipelines become too large."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"The product's development has been stopped. It focuses on maintaining existing products."
"We have rolled out the SAFe model, but what we would like to have is better integration with Agile Central, for instance, or at least at the plugin level, where we would select only certain stories instead of many stories in the sprint."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"Support and pricing for Chef could be improved."
"In the future, Chef could develop a docker container or docker images."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"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."
"It is an old technology."
"If they can improve their software to support Docker containers, it would be for the best."
More Automic Continuous Delivery Director Pricing and Cost Advice →
Automic Continuous Delivery Director is ranked 14th in Release Automation with 5 reviews while Chef is ranked 12th in Release Automation with 18 reviews. Automic Continuous Delivery Director is rated 8.0, while Chef is rated 8.0. The top reviewer of Automic Continuous Delivery Director writes "An automation solution to automate the entire release process but lacks development". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". Automic Continuous Delivery Director is most compared with , whereas Chef is most compared with Jenkins, Microsoft Azure DevOps, AWS Systems Manager, 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.