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."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."
"Chef recipes are easy to write and move across different servers and environments."
"The most valuable feature is the language that it uses: Ruby."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"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."
"We have had less production issues since using Chef to automate our provisioning."
"My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good."
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"The build and release management features are valuable."
"What I like the most about this product is that it's free and it's secure."
"I definitely like the pipelines and the ease of management once you're in an enterprise."
"The most valuable features of Microsoft Azure DevOps are high-level protection. The protection is very important to the customers to prevent eavesdropping. eavesdropping is when a hacker tries to get into the solution. With this solution is it difficult for them to do it."
"The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user."
"The available Kanban board is the best feature for management decisions."
"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."
"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."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"If they can improve their software to support Docker containers, it would be for the best."
"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."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"Since we are heading to IoT, this product should consider anything related to this."
"As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there."
"When converting to DevOps, it was difficult to map."
"With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem."
"I would like to see a bit more project tracking."
"The interface is very bad."
"The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together."
"I would like to see new features added."
"The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
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.
