Automic Continuous Delivery Automation [EOL] vs Chef comparison

Broadcom and Chef are both solutions in the Release Automation category. Additionally, 86% of Broadcom users are willing to recommend the solution, compared to 95% of Chef users who would recommend it.

Automic Continuous Delivery...

Read 13 Automic Continuous Delivery Automation [EOL] reviews

86% willing to recommend

Chef

Read 19 Chef reviews

479 Views
312 Comparison Views

95% willing to recommend

Automic Continuous Delivery...

Chef

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Automic Continuous Delivery Automation [EOL] 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.

To learn more, read our detailed Release Automation Report (Updated: November 2024).

Buyer's Guide

Release Automation

November 2024

Download the complete report

Helped 824,067 peers since 2012

Categories and Ranking

Automic Continuous Delivery...

Average Rating

8.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Chef

Average Rating

8.0

Reviews Sentiment

7.9

Number of Reviews

Ranking in other categories

Build Automation (17th), Release Automation (6th), Configuration Management (17th)

Featured Reviews

it_user779229

Architect at a energy/utilities company with 1,001-5,000 employees

Reduces our time to market considerably with automated and consistent results

Our most important criteria when selecting a vendor are * the size of the vendor itself * how stable the company is * how long they have been in the market * what product suites they have that can help us achieve our goal at the end of the day. We look for partners, not vendors per se, that can help us implement our vision with us, and that's why we like Automic. I give it a good nine out of 10 at this time. The one piece that I think that could help leverage more of the tool is the scripting language barrier at this time. If that's not there, and some of the pieces that could be delivered faster, it might be adopted more out there in the market. I would suggest look at the complete offering that's out there. I would suggest: Prove it out first with the use case that you have. We were not shy in terms of running some proofs of concept with a couple of big vendors out there, and then making them make the case why their product suits our use case. And don't be shy to restart if there is something that you think is not going right, make sure you fix the problem before it gets too late.

Read full review

Arun S .

Senior Consultant at a tech services company with 201-500 employees

Useful for large infrastructure, reliable, but steep learning cureve

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 solution is good to manage multiple large infrastructures. We can have 10 to 10,000 users using this solution and it manages them well.

Read full review

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros

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

"It can support very complex environments and dependencies."

"Gives people insight into what's happening during the deployment."

"We have saved on our time costs and have seen more quality."

"It provides a wonderful user interface which is easy to use."

"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."

"Deployment workflow (WF) can be designed this way, so that it is not necessary to provide all applications (systems) artifacts of which an application consists."

"It gives us good feedback on visualizations and on how our processes have progressed."

More Automic Continuous Delivery Automation [EOL] 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."

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

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

"The scalability of the product is quite nice."

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

"The solution is easy to use and learn, and it easily automates all the code and infrastructure."

"Chef recipes are easy to write and move across different servers and environments."

"The most valuable feature is the language that it uses: Ruby."

More Chef pros

Cons

"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."

"Not a perfect ten because the user interface is brand new and it needs improvement."

"The dashboard should allow you to see the current state of packages in each environment, not only on an individual application basis, but across the entire application platform."

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

"key thing is support for cloud-based deployment. That is lacking."

"At the moment, the version that we are using (version 12.0), the environment is complex with multiple installations. Therefore, the monitoring is not scalable, but this should be improved in 12.1 and 12.2."

"I would like to see more support for WebSphere."

"The stability of the solution can be improved."

More Automic Continuous Delivery Automation [EOL] cons

"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."

"Third-party innovations need improvement, and I would like to see more integration with other platforms."

"If only Chef were easier to use and code, it would be used much more widely by the community."

"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."

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

"If they can improve their software to support Docker containers, it would be for the best."

"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 like to see more security features for Chef and more automation."

More Chef cons

Pricing and Cost Advice

"I can save time and money more quickly."

"If you have a fixed contract, it has limits to spreading out. If you have a flexible enterprise license contract, then you have a lot of scalability for this tool."

"Customers often complain about the price."

"We increased our quality and reduced our time costs."

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

"We are using the free, open source version of the software, which we are happy with at this time."

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

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

"Chef is priced based on the number of nodes."

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

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

"We are able to save in development time, deployment time, and it makes it easier to manage the environments."

More Chef pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Release Automation solutions are best for your needs.

See recommendations

824,067 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

40%

Computer Software Company

19%

Manufacturing Company

Pharma/Biotech Company

Financial Services Firm

23%

Computer Software Company

15%

Manufacturing Company

Retailer

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

Questions from the Community

Ask a question

Earn 20 points

What do you like most about Chef?

Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.

See all answers

What is your experience regarding pricing and costs for Chef?

Chef is priced based on the number of nodes.

See all answers

What needs improvement with Chef?

Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.

See all answers

Comparisons

No data available

BigFix vs Chef

Compared 22% of the time

AWS Systems Manager vs Chef

Compared 18% of the time

VMware Aria Automation vs Chef

Compared 14% of the time

Microsoft Configuration Manager vs Chef

Compared 12% of the time

Microsoft Azure DevOps vs Chef

Compared 12% of the time

More Chef Competitors

Product Reports

Buyer's Guide

Automic Continuous Delivery Automation [EOL]

December 2024

Automic Continuous Delivery Automation [EOL] report

Download Automic Continuous Delivery Automation [EOL] product report

Buyer's Guide

Chef

December 2024

Download Chef product report

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform

No data available

Learn More

Broadcom

Chef

Overview

Deliver apps at pace with agile development and let customer satisfaction soar.

Today, the pressure is on to transform how you deliver applications to market. Get release agility and speed without compromising quality and stability with CA Continuous Delivery Automation. Deliver apps reliably on demand from development through production—mobile to mainframe. Agilely scale as the cadence, volume and complexity of your apps grow. It’s DevOps-ready release management and automation for your dynamic enterprise.

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

BET365, Charter Communications, TASC

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap

Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation. Updated: November 2024.

DOWNLOAD NOW

824,067 professionals have used our research since 2012.

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.