Try our new research platform with insights from 80,000+ expert users
Director at a tech services company with 10,001+ employees
MSP
When you are running a large cluster with hybrid applications, it can be very instrumental in making sure that they are running in sync
Pros and Cons
  • "It is a well thought out product which integrates well with what developers and customers are looking for."
  • "Third-party innovations need improvement, and I would like to see more integration with other platforms."

What is our primary use case?

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.

How has it helped my organization?

When you are running a large cluster with hybrid applications, it can be very instrumental in making sure that they are running in sync. The tools it offers for running in environments has made it a good solution to use.

What is most valuable?

Its most valuable feature is automation.

What needs improvement?

Third-party innovations need improvement, and I would like to see more integration with other platforms.

Buyer's Guide
Chef
November 2024
Learn what your peers think about Chef. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

We put quite a lot of stress on it, especially in our larger environments.

What do I think about the scalability of the solution?

The scalability is good. I have used it for several environments, from small (a couple of servers) to large clusters more than 50 servers). 

What was our ROI?

We have seen a lot of ROI. Our customers really enjoy the tool. We are able to save in development time, deployment time, and it makes it easier to manage the environments.

What's my experience with pricing, setup cost, and licensing?

Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market.

The AWS platform is solid. With the technologies that they offer, it makes it easy to integrate. When you are building environments and your able to integrate everything together, this is good thing.

Which other solutions did I evaluate?

We looked at a combination of open source and other paid solutions. It was hard because Chef offered many options that others didn't, so it wasn't a one-to-one comparison.

Chef had better functionality, flexibility, and price. It is a clean product that is easy to work with and our customers like the product.

What other advice do I have?

It works well. I would highly recommend it. 

It is a well thought out product which integrates well with what developers and customers are looking for.

The product works well with VMware environments.

I have used the on-premise and AWS versions. It integrates well if you are in AWS environments. However, if you are on-premise, it may not be the best solution.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
Ivan Bizhev - PeerSpot reviewer
DevOps Engineer at a comms service provider with 501-1,000 employees
Real User
Top 5
The product has an old technology, though it is useful for automating processes
Pros and Cons
  • "The product is useful for automating processes."
  • "It is an old technology."

What is our primary use case?

We were using the tool for managing Kubernetes.

What is most valuable?

The product is useful for automating processes.

What needs improvement?

I did not like the solution. It is an old technology. Compared to Ansible, it just doesn't hold up because we need to deploy a client to each of the services we need to manage, which makes the automation much harder.

What do I think about the stability of the solution?

The tool was fairly stable.

How was the initial setup?

The product was deployed on the cloud.

What other advice do I have?

I would not recommend the solution to others. It depends entirely on how someone’s system is made, but still, I would probably suggest something else entirely. Overall, I rate the tool a four or five out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Chef
November 2024
Learn what your peers think about Chef. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.
Manager at ZS Associates
Real User
Simple, easy to use, more versatile, can handle a hundred thousand servers at the same time
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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. 

We started using the AWS services, for example, Opsware. Whatever recipes we have written in SAP, we can use the same recipe in Opsware. Moving from one to the other is almost no work.

What is most valuable?

The most valuable features for us would be the writing of the recipes. Any business can write the recipe based on their deployment, it's not like we have to follow a specific path. 

AWS Marketplace gives you a sense of authentic products. Since AWS does its own checks on the marketplace products it's kind of a sense of relief that something will not be problematic.

What needs improvement?

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.

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

It's quite stable, we hardly see surprises. Its deployment is very smooth.

What do I think about the scalability of the solution?

We have many applications and each one has its own cluster of the servers. We have more than a hundred servers and a couple of clusters which is a big environment. We use SAP and they help us. 

How are customer service and technical support?

If we need technical support we raise an AWS ticket and someone from the technical support team helps us. If we hit a roadblock we have to go out beyond AWS support which is fine.

Which solution did I use previously and why did I switch?

The reason that we chose this solution is because it's more effective and it gives us the ability to do the customization that we would like to do. It's also more versatile in the way that we can deploy using this tool, not only on Cloud but at the same time on-prem as well. It's more powerful.

What was our ROI?

We see ROI from saving a lot of time and that our deliveries are now on time. Also, we save the amount of time we take to deploy and make any changes in the deployment and in expediting service. The amount of time invested there is less which in turn we can invest in some other work. So our ROI is speed.

What other advice do I have?

I would rate this solution a nine because it's simple, easy to use, more versatile, and most importantly, it can handle the hundred thousand servers at the same time very easily and almost in no time.

It depends on the enterprise need, but I would advise someone considering this solution that if you want to have very heavy or big clusters this is a product you can trust for deployment and it's smooth. You can create your own custom recipe which in other products, I would say is only partially there and depends on the different types of applications. Not all applications have the same deployment and orchestration patterns and most of the SAP deployment credits are covered. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Primary Architect at Autodesk, Inc.
Real User
It is simple, easy to use, and versatile
Pros and Cons
  • "The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
  • "Deployment has become quick and orchestration is now easy."
  • "Since we are heading to IoT, this product should consider anything related to this."

What is our primary use case?

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

How has it helped my organization?

Deployment has become quick and orchestration is now easy. If you have thousand of servers, you can easily deploy them in a minimum amount of time. You can deploy applications or any type of announcements in a reduced amount of time.

What is most valuable?

Writing recipes, which is great. Any business can write a recipe based on their deployment. We do not have to follow a path.

It is simple, easy to use, and versatile. The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints.

What needs improvement?

Since we are heading to IoT, this product should consider anything related to this.

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

The product is quite stable. We hardly experience any surprises. Its deployment is very smooth.

What do I think about the scalability of the solution?

We have many applications and each is having its own cluster of the service. We have more than a 100 servers and a couple of clusters. That is a big environment.

How is customer service and technical support?

If we need help, we raise an AWS ticket. Then, the AWS support helps us with the technical support.

How was the initial setup?

The integration and configuration of this product in our AWS environment was simple.

What was our ROI?

We are saving a lot our delivery time and on te amount of the time that we deploy. We used to make changes during the deployment. So, the amount of time invested there is less, which in turn, we can invest in some other work. Therefore, our ROI is quick, though it does depend on the size of your service.

What's my experience with pricing, setup cost, and licensing?

Purchasing through the AWS Marketplace was a good place to go to purchase this product because you receive a sense of authenticity with the products. Since AWS has its own checks on AWS Marketplace products, there is sense of relief that the product will not be problematic.

Which other solutions did I evaluate?

We looked at other product like Puppet. We are also using Ansible. However, Chef is the market leader, so we went with that.

Chef is more effective. It provides the hooks, so we can do customization. The product is more versatile. For example, we can deploy using this tool, not only with cloud, but simultaneously on-premise. So, it is quite powerful.

What other advice do I have?

If someone would like to go for a heavy cluster, this is a product they can trust for deployment, since it is smooth. Even though customization is needed, they can create their own custom recipe, which in other products, I would say is partially there and also depends on the different type of applications. 

We had the solution on on-premise for a year, but now it is completely on AWS Cloud. AWS Cloud is easier to use. We can change the solution by refitting the architecture solution now because it is easy.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
MohammedHashim - PeerSpot reviewer
Principal Architect at Brillio
Real User
Provides a centralized management system in a hybrid cloud environment, but needs more analytics and reporting
Pros and Cons
  • "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."
  • "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."
  • "I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
  • "Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."

What is our primary use case?

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.

How has it helped my organization?

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. It works like a centralized broker/control management solution, which has helped broker in a hybrid cloud environment. AWS and Azure just two examples. This cloud platform keeps expanding.

What is most valuable?

The best are some of the default, out-of-the-box capabilities that are available. Plug-ins with multiple vendors and other infra-cloud platforms. The templates are very easy to use. Ease of use, overall, is an advantage of Chef.

What needs improvement?

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. They should make it into a larger toolset.

I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

I have had minor issues with development and configuration but we have an in-house team that takes care of most of it.

What do I think about the scalability of the solution?

My scaling is taken care of, predominantly, with the native capabilities with my cloud. Most of our environments are cloud-first companies, so that has not been much of a challenge.

When I start adding more engines to it, so far I haven't faced issues because I have a different level of scaling up. But in terms of horizontal scalability, like adding more technology, for instance, I think Chef has a ways to go. Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that.

How are customer service and technical support?

Vendor support has been decent. It's okay from that perspective. But sometimes it takes a while. They could have more dedicated support. Sometimes that is a challenge. If my in-house team cannot handle it, getting dedicated vendor support is a challenge and something that comes at a premium. Because they charge us a premium, I use my partner's channel rather than directly with Chef. Except for some proofs of concept and some demos, I haven't used much help.

But presale support was very good.

Which solution did I use previously and why did I switch?

I mostly wrote scripts, predominantly with Python and some others. Compared them, Chef has definitely been more satisfactory.

How was the initial setup?

Setting up initially was quite straightforward. What was challenging was when our platforms kept changing. We had an on-premise environment and we evolved to the cloud world. Then there was AWS and Azure. We keep adding and expanding. Maybe we haven't thought much about our architecture - that's been through some changes. And maybe the horizontal capabilities I was talking about earlier, the scalability might be another aspect. But the initial setup itself was quite straightforward.

What's my experience with pricing, setup cost, and licensing?

There are some flexible pricing models which you get from multiple partners, and then we bundle our solution. From that perspective, it is okay so far. But maybe when we go to the enterprise level, there will be components we have to pay for, when it comes to DevOps with customers who already have an existing license. Those things are always complicated. But otherwise, for regular commercial licensing, it can be flexible.

Which other solutions did I evaluate?

We used SPO Orchestrator. And before Chef there was one proof of concept with Puppet but for some reason, Puppet was not as developer-oriented. Many of our in-house people found Chef to be more user-friendly, from an administrative perspective, so we narrowed it down to Chef.

What other advice do I have?

If you're looking for an environment where there is an ROI business case, or looking into or orchestrating multiple environments, it makes sense to go with Chef. But if it's a minor orchestration you're looking into, the best tool would always be native solutions. In other words, if I you are looking at a platform where there will be two or three moving parts, you should look at the platform's built-in, native solution. If you have a wider range of moving parts and automation to be done, configuration-wise, you can bring in an orchestrator like Chef.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
CTO at FCamara
Real User
It integrates with many products in ILT and data management areas with each of them providing cloud computing
Pros and Cons
  • "The most valuable feature is automation."
  • "The AWS monitoring, AWS X-Ray, and some other features could be improved."

What is our primary use case?

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

How has it helped my organization?

My clients are happy, which is the most important thing.

What is most valuable?

The most valuable feature is automation. 

What needs improvement?

The AWS monitoring, AWS X-Ray, and some other features could be improved.

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

We have some issues in Brazilian region with stability. However, in US region, we have no issues with stability.

What do I think about the scalability of the solution?

Scalability is pretty good. We have nothing to complain about, except the price.

How is customer service and technical support?

I would rate the technical support as a ten out of ten.

Amazon is a great partner.

How was the initial setup?

The integration and configuration are pretty good in the AWS environment. The problems are usually on our side, not on AWS' side.

What's my experience with pricing, setup cost, and licensing?

The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it. 

Which other solutions did I evaluate?

I don't like some of the products offered by VMware. I like the automation offered by Chef and Puppet.

We chose Chef because some clients have some legacy systems and decided to work with them. We don't really like work with VMs, but when we have to, we use Puppet.

What other advice do I have?

I have used the on-premise and AWS versions. I prefer the AWS for troubleshooting.

It integrates with many products in ILT, data management, and the server areas with each of them providing cloud computing, like EC2 and API Gateway.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
PeerSpot user
Senior DevOps Engineer at a tech services company with 1,001-5,000 employees
MSP
Enabled us to completely eliminate manual deployments
Pros and Cons
  • "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."
  • "If only Chef were easier to use and code, it would be used much more widely by the community."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

Configuration management is the most useful feature and is used by everyone. Provisioning is also an important feature. Since Chef collects a lot of inventory using Ohai, the inventory can also be used to integrate with third-party tools.

Although deployment can be done a lot better with other tools on the market, Chef also accomplishes this. However, remember that rollback can be problematic here.

What needs improvement?

In my presentation to SAP engineering, Ansible was chosen over Chef by all the admins for one reason: simplicity. If only Chef were easier to use and code, it would be used much more widely by the community.

What other advice do I have?

Chef is an extremely amazing tool and has been extensively developed in the last couple of years. There are tons of plugins and integrations available for it, my favorite being the Chef-docker plugin.

I started with Chef as a QA engineer and wrote some beginner level recipes for some easy setups on AWS. I then worked on a bank project where I used the knife-vcloud plugin for Chef to automate provisioning for VMware vCloud. I did some initial evaluation, comparing Chef and Ansible for SAP to automate deployment on bare metal. In some recent projects, I wrote Chef recipes for deployment automation. I integrated it with Fabric/Python. 

I would definitely rate Chef an eight out of 10. Although Chef is easy to code, it still has a little learning curve, since you need to know Ruby.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Murat Gultekin - PeerSpot reviewer
Presales Consultant - Solution Architect at Hewlett Packard Enterprise
Real User
Easy to install configuration management and automation tool with a good compliance feature
Pros and Cons
  • "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."
  • "Support and pricing for Chef could be improved."

What is our primary use case?

Chef is mostly for the operating systems to deploy or style, e.g. not containers. Before the containers, you need hardware, then an operating system, then you start to work on Kubernetes. To automate those steps, we use Chef.

The tool is useful for provisioning the operating system, because as you talk about the ops, sometimes customers ask to further deploy everything through automation, e.g. starting from scratch. You need to use different tools for you to provision via automation, so you need Chef. We use an automation tool such as Chef, then we were able to run Docker or containers on top of the hardware and operating system.

What is most valuable?

The features are good in Chef, especially its compliance feature. It's very good and it's what I found most valuable in the tool.

What needs improvement?

Support and pricing for Chef could be improved.

For how long have I used the solution?

We've been dealing with and providing Chef to our customers for three years.

What do I think about the stability of the solution?

I'm satisfied with the stability of Chef. I'm satisfied with its performance, but it's the same with some of its competitors, e.g. there are alternatives. Ansible from Red Hat is also a good tool. We are also using it. The tool we use depends on the use case and the customer, e.g. we can use different tools.

What do I think about the scalability of the solution?

Chef is a scalable tool.

How are customer service and support?

Support for Chef could be better. It needs improvement.

How was the initial setup?

The initial setup for Chef was easy. The tool is easily installed. Installation could take a few hours. It's the implementation of the tool that takes time, because if you need to scale up, you need to integrate it with other products, and that can take time.

What's my experience with pricing, setup cost, and licensing?

Pricing for Chef can be relatively high for some customers but, if we consider the benefits it provides, we can say that it is a reasonable price. . Customers need to pay for the license of the tool on a yearly basis.

Which other solutions did I evaluate?

We were able to evaluate Terraform and Ansible.

What other advice do I have?

For automation and configuration management, we are using several tools: Terraform, Chef, and Ansible for provisioning. We are using those products, and they are good. They are not for container management, but for provisioning and deploying applications, software, and hardware. We are also using them for automation.

Chef is a configuration management tool.

I can recommend Chef to others who want to start using it. I can also recommend other products, e.g. Ansible, but most of the tools which are competitors of Chef and have the same functions are also good.

I'm giving Chef a rating of seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Download our free Chef Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free Chef Report and get advice and tips from experienced pros sharing their opinions.