We performed a comparison between Chef and Microsoft Azure DevOps 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."Deployment has become quick and orchestration is now easy."
"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 most valuable feature is the language that it uses: Ruby."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"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."
"There are a lot of helpful features available for tracking dependencies."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"The user interface is very friendly."
"I like the tracking and that we can monitor our velocity."
"I found the Kanban board to be the most useful for my needs."
"Provides agile management of projects."
"The solution integrates well with other Azure services and third-party tools."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"It is an old technology."
"If they can improve their software to support Docker containers, it would be for the best."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Since we are heading to IoT, this product should consider anything related to this."
"In the future, Chef could develop a docker container or docker images."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"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."
"There could more integration with other platforms."
"There are some areas that need improvement such as tracking."
"Its testing features are limited and can be improved a little more. They should provide more options from the testing and build perspective. Currently, we have to use a third-party product for testing. It would be great if it has more than one testing tool."
"More features can be included."
"The administrative capabilities of the tool need a huge improvement. Its Wiki and reporting also need a lot of improvement. Their support can also be better."
"Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T."
"I would like to see better interoperability with the agile scaling frameworks."
"Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy."
Chef is ranked 15th in Release Automation with 18 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 127 reviews. Chef is rated 8.0, while Microsoft Azure DevOps is rated 8.2. 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 Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Configuration Manager, SaltStack and BigFix, whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management. See our Chef vs. Microsoft Azure DevOps 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.
