2018-07-01T08:03:00Z

What is your primary use case for Chef?


How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

Guest
1313 Answers

author avatar
Real User

* For software management * Competitive deployment * Upgrade

2018-12-11T08:31:00Z
author avatar
Real User

We use it for training.

2018-12-11T08:31:00Z
author avatar
Real User

We use it for deployment of applications. It is a tool that you can use on the back-end for deploying architectures. I have used the product for a couple years. I used to work for an online data center, and we used Chef for a lot of the tools and appointments.

2018-12-11T08:31:00Z
author avatar
Real User

It's for deployment and configuration automation.

2018-12-11T08:31:00Z
author avatar
Real User

We use it for integration management.

2018-12-11T08:31:00Z
author avatar
Real User

We use it for provisioning Adobe Experience Manager web application environments.

2018-12-11T08:31:00Z
author avatar
Real User

Our primary use case of this solution is for the orchestration of the service deployment, and integrations. Earlier, we had it on-prem but now it's totally on AWS cloud. AWS cloud is easier to use, and changing and refitting the architecture solutions is very easy.

2018-12-10T06:53:00Z
author avatar
Real User

I have used in my current company for three years, and with other clients for more than ten years.

2018-12-09T08:49:00Z
author avatar
Real User

It is for orchestrating our servers and deployments to do integrations.

2018-12-09T08:34:00Z
author avatar
Top 20Real User

We use it for provisioning and ongoing configuration management. We provision boxes with Chef by taking a base AMI that already has Chef installed, and already has the appropriate credentials to connect to the main server. Then, this will be able to roll out and deploy the configuration. In addition, it runs every five minutes, so any unexpected changes to the configuration get automatically reverted. This means, you get developers, who go into the box and change something, thinking it will be okay. Then, they come to you, asking "Why isn't this change that I'm making working?" We have to explain, "Because it shouldn't be going into the box in the first place."

2018-12-05T07:52:00Z
author avatar
Top 20Real User

Our primary use case is having the properties set up across the servers. We have Chef recipes deployed and configured across our servers, so we get the same type of replication across our servers and environments. We are using the on-premise version. We have our applications already set up for on-premise. We are using Chef and preparing it for CI/CD and other properties. Now, we are planning ahead and will use the AWS service too.

2018-12-05T07:52:00Z
author avatar
Real User

My primary use case for Chef has been always for infrastructure provisioning. For example, infrastructure as a cloud, provisioning it in a multi-cloud environment. That's predominantly what we're using Chef for.

2018-08-02T11:48:00Z
author avatar
Consultant

I used Chef for server provisioning in AWS using the knife-aws plugin. I also used Chef as a configuration management tool. It did all the setup and configuration for all the software packages for multiple servers. To make any updates to the server setups, all we did was update the recipes on the Chef Server.

2018-07-01T08:03:00Z
Learn what your peers think about Chef. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
438,246 professionals have used our research since 2012.