Automic Continuous Delivery Director vs Chef comparison

Cancel
You must select at least 2 products to compare!
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed Release Automation Report (Updated: March 2024).
765,386 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"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."

More Automic Continuous Delivery Director Pros →

"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."

More Chef Pros →

Cons
"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."

More Automic Continuous Delivery Director Cons →

"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 Chef Cons →

Pricing and Cost Advice
  • "There is a free trial available that people can try. The solution has a subscription and it is based on the users that use the solution."
  • More Automic Continuous Delivery Director Pricing and Cost Advice →

  • "When we're rolling out a new server, we're not using the AWS Marketplace AMI, we're using our own AMI, but we are paying them a licensing fee."
  • "The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
  • "The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it."
  • "Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
  • "We are able to save in development time, deployment time, and it makes it easier to manage the environments."
  • "We are using the free, open source version of the software, which we are happy with at this time."
  • "I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
  • "Pricing for Chef is high."
  • More Chef Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
    765,386 professionals have used our research since 2012.
    Questions from the Community
    Top Answer: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.
    Top Answer:There is a free trial available that people can try. The solution has a subscription and it is based on the users that use the solution. The price of the solution can be flexible and there are not any… more »
    Top Answer:Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more.
    Top Answer:Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
    Top Answer:Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
    Ranking
    14th
    out of 32 in Release Automation
    Views
    146
    Comparisons
    61
    Reviews
    1
    Average Words per Review
    281
    Rating
    9.0
    12th
    out of 32 in Release Automation
    Views
    664
    Comparisons
    461
    Reviews
    5
    Average Words per Review
    350
    Rating
    6.8
    Comparisons
    Also Known As
    CA CDD, CA Continuous Delivery Director
    Learn More
    Overview

    CA Continuous Delivery Director is a powerful pipeline planning, orchestration and analytics solution that enables teams to eliminate spreadsheets, automate test processes and continually improve the delivery of revenue-generating features to end customers. The solution works with the most popular commercial and open source DevOps solutions to orchestrate the pipeline from planning through production. It is also the core of the continuous delivery ecosystem from CA, which includes development, testing and deployment solutions. CA Continuous Delivery Director enables effortless continuous delivery of high-quality, innovative applications from high-performance, collaborative teams.

    Chef, is the leader in DevOps, driving collaboration through code to automate infrastructure, security, compliance and applications. Chef provides a single path to production making it faster and safer to add value to applications and meet the demands of the customer. Deployed broadly in production by the Global 5000 and used by more than half of the Fortune 500, Chef develops 100 percent of its software as open source under the Apache 2.0 license with no restrictions on its use. Chef Enterprise Automation Stack™, a commercial distribution, is developed solely from that open source code and unifies security, compliance, infrastructure and application automation with observability. Chef provides an unequaled developer experience for the Coded Enterprise by enabling users to express infrastructure, security policies and the application lifecycle as code, modernizing development, packaging and delivery of any application to any platform. For more information, visit http://chef.io and follow @chef.

    Sample Customers
    United Airlines
    Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
    Top Industries
    No Data Available
    REVIEWERS
    Computer Software Company30%
    Comms Service Provider20%
    Non Tech Company10%
    Legal Firm10%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company13%
    Manufacturing Company8%
    Government8%
    Company Size
    No Data Available
    REVIEWERS
    Small Business5%
    Midsize Enterprise35%
    Large Enterprise60%
    VISITORS READING REVIEWS
    Small Business18%
    Midsize Enterprise12%
    Large Enterprise69%
    Buyer's Guide
    Release Automation
    March 2024
    Find out what your peers are saying about GitLab, Microsoft, Red Hat and others in Release Automation. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    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.