Senior Consultant at a tech services company with 201-500 employees
Real User
Top 5
2023-02-14T12:30:57Z
Feb 14, 2023
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.
DevOps Engineer at a manufacturing company with 1,001-5,000 employees
Real User
Top 5
2023-09-18T15:42:00Z
Sep 18, 2023
The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools.
Presales Consultant - Solution Architect at Hewlett Packard Enterprise
Real User
2022-04-05T19:28:23Z
Apr 5, 2022
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.
Engineer II at a transportation company with 10,001+ employees
Real User
2018-12-11T08:31:00Z
Dec 11, 2018
It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves.
This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time.
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.
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.
Senior DevOps Engineer at a tech services company with 1,001-5,000 employees
MSP
2018-07-01T08:03:00Z
Jul 1, 2018
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, 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...
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 is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
The product is useful for automating processes.
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.
The most valuable feature is the language that it uses: Ruby.
It is a well thought out product which integrates well with what developers and customers are looking for.
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 scalability of the product is quite nice.
It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves.
This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time.
The most valuable feature is automation.
The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints.
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.
Chef recipes are easy to write and move across different servers and environments.
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.
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.