We performed a comparison between Chef and Spring Cloud based on real PeerSpot user reviews.
Find out in this report how the two Configuration Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The ability to send configurations to our systems is valuable, particularly as we don't have a regular Windows AD server. Our current environment doesn't have a Windows AD, which limits our ability to push GPOs. However, this is where the solution can step in and help us push policies."
"While I don't think you can ever have full visibility and control, Intune certainly allows us to see the applications being used and tells us if things like Windows patches aren't applied to machines. It does a good job. That visibility makes life a little easier."
"The stability is good."
"The central administration con dashboard is very easy to use and provides very good oversight on all that needs to be monitored."
"The most valuable feature is the UEM capabilities."
"I like that it's very good and very simple. I found that we just needed to have a proper subscription for an Intune tenant, and from the subscription, if we have the right role assigned, like the global admin role or the owner role, we can use Microsoft cloud resources. With the help of that, we can do many things like setting up Microsoft Intune in the cloud to create our virtual machines. All these can be done, and the steps are very simple. I really liked it. I like features like Windows Auto-Enrollment. I like it very much because whenever you supply it to the end-user, it will be ready to use immediately. The end-user only needs to provide the user credentials, and then they are good to go. I also really like Cloud PC, which was recently launched on Azure."
"The ability to switch between Affinity and non-Affinity enrollment is great."
"The solution has reduced the risk of security breaches by 30%."
"Deployment has become quick and orchestration is now easy."
"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."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most valuable feature is automation."
"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."
"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 most valuable feature is the language that it uses: Ruby."
"The solution's initial setup is straightforward. The deployment process took me around ten minutes to fifteen minutes."
"Spring Cloud integrates well."
"It offers excellent scalability."
"I would like some integration with the Microsoft reporting platform Power BI."
"Reporting in Microsoft solutions is pathetic. With Intune, I'm getting a free inventory tool, but I don't get a reporting tool. When I go to Intune, I can see one machine's entire data in terms of the hardware and the software running on it, but I cannot generate a report for all the machines in the organization. The reporting is the only feature holding back the functionality that is already there."
"I would like the ability to install the agent on devices from suppliers, which would enable us to implement a zero-trust strategy for guest devices."
"Onboarding of endpoint devices is not straightforward. The onboarding process was a little heavier than I thought it would be. That's the key improvement area. Obviously, the more control you have over the devices, the better it is."
"Due to the abundance of features, there's a lot to organize, which makes managing and setting up the solution challenging. The setup is immense, and it would be good to see improvement in this area."
"The scalability could be improved, and like most other MDM products, Intune is good but not 100% there yet."
"Intune should be much more granular in terms of supporting more Android cellular devices."
"The security features should be improved."
"It is an old technology."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"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."
"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."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"I would like to see more security features for Chef and more automation."
"The solution could improve in managing role-based access. This would be helpful."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"If there's a dashboard like the ones provided by Apigee or Kong, that will be useful."
"Stability is one area in the solution that needs to improve."
"It would be beneficial for the framework to become more lightweight and efficient when transitioning to the cloud."
Chef is ranked 16th in Configuration Management with 18 reviews while Spring Cloud is ranked 19th in Configuration Management with 3 reviews. Chef is rated 8.0, while Spring Cloud is rated 6.6. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of Spring Cloud writes "Though the initial setup phase is straightforward, its stability needs to improve". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack, whereas Spring Cloud is most compared with AWS CloudFormation, HashiCorp Terraform and Red Hat Ansible Automation Platform. See our Chef vs. Spring Cloud report.
See our list of best Configuration Management vendors.
We monitor all Configuration Management 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.
