Chef

(35)
4.1 out of 5 stars

Chef turns infrastructure into code. With Chef, you can automate how you build, deploy, and manage your infrastructure. Your infrastructure becomes as versionable, testable, and repeatable as application code.

Work for Chef?

Learning about Chef?

We can help you find the solution that fits you best.

Chef Reviews

Request More Information
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 35 Chef reviews
LinkedIn Connections
Chef review by Christopher M.
Christopher M.
Validated Reviewer
Review Source

"Chef'ing up Liferay"

What do you like best?

I like chef because it uses DSL for configuration instead of XML, Rackspace supports it very well, etc. However the absolute best thing about Chef is the concept of recipes where you can get your platform up and configured extremely easily if that platform has a chef recipe. In addition most large platforms do have chef recipes so it's great! Also, I like that it;s open source

What do you dislike?

Some of the things i dislike about chef, and this might jkust be a criticism of configuration management in general, is that you need pretty much a full team to support it. Sometimes I feel like it adds more complexity instead of kless.

Recommendations to others considering the product

Learn it well before you try to incorporate it in your enterprise

What business problems are you solving with the product? What benefits have you realized?

The biggest issue we are solving with Chef is the knowledge gap that exists in new employees when first learning out platforms. previous it would take months for new developers to become effective because they spend several months fighting with the platform, build tools, etc. Chef makes this much less of a hassle

Sign in to G2 Crowd to see what your connections have to say about Chef
Chef review by Phil A.
Phil A.
Validated Reviewer
Verified Current User
Review Source

"Longtime user and fan of Chef"

What do you like best?

The Chef DK allows you to have a full CI/CD workflow for your infrastructure as code. With chef you can stick to the community cookbooks and boilerplate resources or you can make it do anything you like with raw ruby.

What do you dislike?

As everyone says it can be a bit daunting to get started. Most new development seems to be targeted at enterprises.

Recommendations to others considering the product

It's worth spending a bit more time up front to understand the product than you might with other configuration management solutions. The benefit is much more power and a massive community.

What business problems are you solving with the product? What benefits have you realized?

With Chef, there's no excuse not to have your entire infrastructure as code.

What Configuration Management solution do you use?

Thanks for letting us know!
Chef review by Sahil S.
Sahil S.
Validated Reviewer
Verified Current User
Review Source

"Best tool for unifying development environment in a large team."

What do you like best?

Chef provides tools for for IT automation and after trying other tools. Its a master client model and is based in Ruby which was really helpful since we were also developing applications in Ruby on Rails.

The best thing about chef is the collection of modules and configuration recipes. Also, its based around Git which everyone is familiar with and 'Knife' tool is very helpful during installations.

What do you dislike?

Learning curve is steep but since we were already using Ruby it was a bit easy for us. Apart from that, its a not a smiple tool, It can lead to very large code bases and complicated environments quickly. One needs to be aware of that. Also, it doesn't support push functionality which other alternatives does.

Chef documentation can also be a little sketchy from time to time. They are more focused on making it work than writing documentations and doesn't provide as much platform support as other alternatives does.

What business problems are you solving with the product? What benefits have you realized?

We use chef's Application Automation tool 'Habitat' to unify the development enviroment among a large team which can be a disaster while working with frameworks like Ruby on Rails.

Chef review by Kevin V.
Kevin V.
Validated Reviewer
Verified Current User
Review Source

"Great tool for system configuration management"

What do you like best?

Chef is pretty solid for configuration management of Windows machines and ensuring that they are all setup and provisioned the same way. The setup and scripting of recipes is pretty extensive, and Windows support is solid. There are a variety of recipes to do most windows configuration needed, as well as Linux.

What do you dislike?

The setup is pretty complex, it can take awhile to just setup a server and figure out how to connect a client to it. It would be nice to have more functionality exposed in the Chef GUI, using command line for a majority of tasks can be tedious at times. Chef is mainly geared toward ensuring a server is configured properly, but it would be nice to have the option for 'one off' tasks. When you have agents already running on your systems for Chef it would be nice to run a task on a subset of machines instead of yet another agent and management system for that. It also runs best if you have a person dedicated to the configuration and on going maintenance of Chef. It takes some effort to keep up on your recipes.

Recommendations to others considering the product

If you are using Azure, check out Microsoft's Azure lab on setting up Chef, it significantly speeds up the implementation process. Be sure to run through some tutorials and documentation on the Chef website as it is very difficult to setup straight out of the box. There aren't really any wizards or in-product tutorials.

What business problems are you solving with the product? What benefits have you realized?

Chef solves the system configuration management issue pretty well, it is able to ensure that machines are setup similarly. The 'configuration as code' aspect makes it clear to the organization what is involved in setting up and configuration of a server. It helps to document the process as long as you follow through on continuously adding recipes as you move along.

Chef review by Renato Augusto T.
Renato Augusto T.
Validated Reviewer
Verified Current User
Review Source

"deploy made easy again "

What do you like best?

Previously to deploy a large application was suffering, always happened several problems. When I met Chef (while studying the vagrant) quickly deployed in my company. Chef is able to handle EVERYTHING related to creation of a dynamic infrastructure

What do you dislike?

Nothing, all in Chef is exquisite, even the price is right. Of course you will have to study hard for put the tool into production, but it is a study that will be worth it.

Recommendations to others considering the product

Know that the documentation is extensive. It will take time to master the full tool, but the time spent will be saved in deploy

What business problems are you solving with the product? What benefits have you realized?

DevOps! In my company we had problems in the deployment of the tools. The time between the development and deployment was too long, now with Chef dramatically reduce the costs associated with deployment, and now we have the DevOps culture more strong

Chef review by Liam B.
Liam B.
Validated Reviewer
Verified Current User
Review Source

"Chef is an excellent tool for Server Configuration"

What do you like best?

I have been using Chef as it helps me to automate my applications in configuring and getting deployed in my web network easily.

It has got various features such as Chef Management console, Chef Analytics, and Client Reporting. It helps me to keep my server up all the time and saves up a lot of time in this area.

It also allows me to keep the track of my applications in terms of version control. So, the applications remains in synchronization with the help of different versions available for each built.

What do you dislike?

The setup document and tutorials could have been a little better. They have provided all the documentation in a single web page with no references to any external links.

Recommendations to others considering the product

I would recommend you to choose between the free version and the paid version of Chef as per your needs and requirements. Getting an initial demo from the team would be a good idea.

What business problems are you solving with the product? What benefits have you realized?

We are using it for the automation for our server configuration which saves a lot of time and energy required for manual configuration each time the server gets down. I like the Chef Development Kit where all the command line tools are available for help if you are stuck somewhere.

Chef review by M. Serhat D.
M. Serhat D.
Validated Reviewer
Verified Current User
Review Source

"Made for DevOps and Easy Deployment"

What do you like best?

Chef is one of my favorite tools lately. It makes painful and risky deployments easy and fast. Chef is also providing a quite flexible infrastructure which lets you to manage many nodes easily. You can simply integrate your other DevOps practices with Chef. It helps you to understand your infrastructure better and minifies security risks before your service goes down. Definetely Chef is a great tool to minimize your downtime. I'm a Ruby developer and Chef has a good support for both Ruby and Rails environments. Also Chef recipes written with Ruby, which is time saving for me.

What do you dislike?

Hosted and premium versions are more expensive than I can afford. Also management console, analytics and high availability features are not included in free version.

Recommendations to others considering the product

Before going with Chef, I suggest you to read well written documentation first and then check cookbooks for ready-to-use solutions before writing your own.

What business problems are you solving with the product? What benefits have you realized?

Chef makes our deployments easy and efficient. In the past deployments were stressful and time-consuming for us and Chef helped us to deal with deployments. Also check and read about Puppet, Ansible, Capristano and other DevOps tools which you can use together with Chef.

Chef review by Nagarjuna Y.
Nagarjuna Y.
Validated Reviewer
Verified Current User
Review Source

"Devops made easy"

What do you like best?

Awesome documentation & training resources given by the Chef are easily understandable.I have used only the opensource and free versions of chef-solo (except for the trail period) in all the organisations I have worked with till now.I use chef in conjunction with vagrant to improve & automate the stuff in development life cycle.Librarian-chef is most useful bundler plugin for chef based infrastructure which one must try automates the things with simple commands.

What do you dislike?

They divided the Chef tool into three categories for the sake of business which is very disappointing

1. Hosted Chef

2. Enterprise (On-Premise Version)

3. Opensource Version which comes with less add-on and no support

Though there is a vast community present who are using chef for businesses it tuff to rely on opensource chef unless we have very experienced professionals.Pricing disappoints me a lot being a small organisation.Chef commitment to opensource is still doubtful which is an scary thing.

Recommendations to others considering the product

Do you wanna save the amount of time managing server configuration for your systems? Then yes I would recommend Chef for you.For small organisation hire a experienced professional to save money that need to be spend on tech support while using chef otherwise train them to get expertise so that they can confidently manage your infrastructure.

Choosing Hosted chef is best option for the organization with newly trained staff which would save organisation from critical situations.

What business problems are you solving with the product? What benefits have you realized?

Cloud Deployment, Build Automation, Server configuration Management

Chef review by Evan W.
Evan W.
Validated Reviewer
Verified Current User
Review Source

"Infrastructure as code never looked so intimidating and yet hopeful"

What do you like best?

The ability to code infrastructure and then run it in action from a single line command is amazing. Imagine spinning up not just 1, but an entire stack of services at once (a whole ecosystem). That's the power of Chef.

What do you dislike?

The problems are myriad. Chef does not have an easy way to pick up for beginners. Most cookbooks are focused on Linux, not Windows. And whenever a deployment breaks, tracing it is a huge pain as there stacktrace is not very informative.

What business problems are you solving with the product? What benefits have you realized?

Chef solves the problem of continuously updating and deploying your software ecosystem from scratch for different purposes and even clients. This helps to make infrastructure development verifiable and repeatable.

Chef review by Todd P.
Todd P.
Validated Reviewer
Verified Current User
Review Source

"Chef is Awesome!"

What do you like best?

The shear amount that you can do with the product from Linux to Windows, configurations to application deployments, Chef is delightfully AWESOME!!!!!

What do you dislike?

I personally don't have any dislikes for Chef as a product. The only caveat is when creating resources, you'll need to increase your Ruby knowledge and skills.

Recommendations to others considering the product

To learn Chef, I highly recommend using the http://learn.chef.io . Even for an OPs guy, Chef is awesome!

What business problems are you solving with the product? What benefits have you realized?

When I jumped on the infrastructure as code bandwagon, I was testing both Chef and Puppet to Linux and Windows deployments. I chose Chef as they fixed a pending reboot issue with RDSH first. As a Solution/managed Service provider, the ability to reduce deployment time with a standard automated deployment methodology is invaluable.

Chef review by Mario C.
Mario C.
Validated Reviewer
Review Source

"Automating deployment with Chef"

What do you like best?

Chef is a standard in automated deployment. Is used in Facebook and it's really REALLY powerful. It's a very serious thing about deployment automation and it's capabilities are huge. Maintains states (software, configuration...) of the entire cluster, and I'm talking about hundreds of nodes. Cookbooks are very popular and you can find them to do almost everything in the open source community.

What do you dislike?

Chef is terribly complex to deploy by itself, not only needs a Chef Server that internally will install a RabbitMQ, a SQL database, a Nginx... it can really take a lot of resources of your machine.

Not only this, you need to install a daemon, Chef Client, on each Chef node you want to manage. Of course if this Client fails... your node is "lost" for Chef and you cannot manage it anymore until you restart the client.

Recommendations to others considering the product

If you really, really need to manage a big set of nodes to do very complex things, you can give Chef a try (you also have Puppet). But if need something relatively simple I don't think is worth the effort. As I mention before, Chef is quite complex if you want to do simple things (maybe Ansible fits better in this case)

What business problems are you solving with the product? What benefits have you realized?

We were automating the installation of 8 to 10 linux packages over a set of 4 to 20 machines. We were using a "root" machine to start the installation and, using a web ui, let a user select a set of technologies to install them on the rest of the nodes.

Chef review by Michael M.
Michael M.
Validated Reviewer
Review Source

"Powerful tool but difficult to get started with"

What do you like best?

Simplifies bootstrapping fleets of servers and managing required packages. Allows developers to build upon a library of packages from other developers so they don't need to start at the basics from scratch and can more quickly and easily start on the parts that really matter

What do you dislike?

Very difficult and time consuming to set up and get started with; large learning curve; compatibility issues with little to no documentation

Recommendations to others considering the product

Consider as a possible solution for your DevOps build but also consider other tools like Ansible. You may very quickly become dependent on Chef once you implement it so make sure you like it and it meets your needs first. Team members with previous experience will be a huge plus to overcome the initial learning curve and setup time.

What business problems are you solving with the product? What benefits have you realized?

Automating deployments, versioning deployment code, granular user permissions, scalable and highly available infrastructure and applications

Chef review by Ashutosh N.
Ashutosh N.
Validated Reviewer
Review Source

"Chef is neat and awesome"

What do you like best?

Open Source

Community support.

Documentation is great.

Well written Chef blogs to understand steps and procedure.

Automated deployment of application in a farm.

Availability of well written cookbooks.

Ease of development with just enough knowledge of Ruby.

What do you dislike?

Installation should be made little faster.

knife-plugins support is less

Some of the cookbooks are not maintained..

Recommendations to others considering the product

I recommend to use Chef because of following reasons :

Community support is amazing. You have developers/users in the list who help to solve your problems. You need not be proficient in Ruby, just know-how of Ruby is enough to start developing recipes. Most of the cookbooks available on Chef's git-hub page can be re-used and customized as per your requirement. It also supports majority of Operating Systems. I have worked with other configuration management and remote execution systems, but it all depends what your need is and which one fits your environment. Rather than wading through so many tutorials, decide on one and be on it.

What business problems are you solving with the product? What benefits have you realized?

We wanted to do one-click installation of application on cloud.

Did a setup right from bare-metal provisioning and then used Chef for application deployment on Private Cloud. Developed shell scripts which triggers chef-client once a machine is ready on blade server. Used knife-plugins to manage private cloud farm.

Some of the benefits realized were ease of testing cookbooks using test-kitchen and Vagrant. Chef-solo was also helpful.

Chef review by Rodrigo R.
Rodrigo R.
Validated Reviewer
Review Source

"Excelent server automation tool"

What do you like best?

There are plenty of well written, documented and supported Chef recipes for dealing with all sorts of server automation, like users management, database management, Solr configuration, full application stack configuration (Sensu, Gitorious, Redmine), SSH, and many more commonly used software. All of them are open-source and have plenty of customization options. Chef itself has good documentation.

Dependencies management is very easy and robust by using librarian-chef.

Chef's verbose mode is very helpful when debugging what a recipe is doing and there's also a dry runner mode which won't actually run anything in the server, which is also helpful in some cases.

Unlike Puppet there's no domain specific language to learn, which is a big advantage for me. You only have to learn a bit of Ruby, which is an easy language to learn and use and you are able to perform any logic pretty easily when compared with Puppet which is quite limiting when you need some custom logic which is not handled by their DSL and you are forced to extend their DSL.

Chef can be configured through an specialized server that will orchestrate all managed servers or they can be used without setting up any Chef server, through chef-solo. Chef-solo can be integrated with Vagrant as well to help setting up a development environment very quickly.

What do you dislike?

I'd prefer Chef's focused on chef-solo for most of its beginning tutorials as I find it the easier mode to start with and also the most useful one for most small organizations. The fact that chef-solo is not the tutorials assume makes it harder for a beginner to understand how it works.

I also think they could be more backwards compatible in new releases. I remember it took me quite a while to fix some old recipes I had so that it would work in newer Chef releases...

They use JIRA to manage their tickets and I really don't like JIRA.

Recommendations to others considering the product

I'd recommend starting with the chef-solo mode, which is much easier to start with and well suitable even for more complex servers infra-structure. Also, take some time to learn some Ruby if you are not comfortable with the language.

What business problems are you solving with the product? What benefits have you realized?

We integrate Chef and Capistrano to manage our servers and deploy our applications. Since both are written in Ruby, we can share a dynamic configuration written as a Ruby DSL that is used by both Chef recipes and Capistrano tasks. We use Capistrano to run Chef in the servers requiring changes.

For example, we manage multiple environments and applications in a shared set of servers. We have a database server and two application servers and we are able to properly manage the database in the database server through Chef, configure Solr, install packages in the application servers, set up nginx in the right server and everything that is required for the application to run and finally run the deploy procedure using Capistrano tasks, which are more well suited to handle deploys and rollbacks than Chef is. The server management part is handled by Capistrano running chef-solo in the right servers. Then the deploy proceeds as usual with regular Capistrano tasks. All with a single command line that will inform the application, which application server to deploy to and the environment (production, Cert, experimental, staging and others).

Being able to run a single command to handle the full deployment cycle gives a lot confidence specially because there are lots of steps involved for our applications to be properly configured and run in our servers... It would be really easy to forget some of those steps in a big release without the automated recipes.

Chef review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Vagrant User"

What do you like best?

I won't state how much I like chef due to its automation, but I'd like to say that in comparison with puppet and ansible, it gives better control as it allows you to "develop" your system. The dependencies system that's out of the box due to Ruby is really good! As a vagrant only user, chef-zero was the product that I really needed!

What do you dislike?

- I have to write ruby

- As a vagrant user, it feels it has quite some overhead when the system bootstraps

- It takes more time to write something "quick and dirty", while ansible performs better for MVP cases

- As a vagrant user, it feels ugly the way I have to manage my secret files, databags are not the best case

Recommendations to others considering the product

Make it being easier to bootstrap new projects - MVPs, maybe use some template bucket?

What business problems are you solving with the product? What benefits have you realized?

As a team leader, I've manage to create a unified environment for my team members, and having it on git, we are having the opportunity to all extended based on our ongoing needs. Using chef like that, It also gives me the opportunity to have a "shared communication protocol" with the devops side, and not missing any details that have been developed throughout the development phase.

As a business perspective, it has make the dev environment "disposable", as everything that's needed run in the Dev's VM and their laptops have no value now, or worrying if they got stolen

Chef review by User in Internet
User in Internet
Validated Reviewer
Review Source

"DevOps Engineer at Refinery29"

What do you like best?

Chef is an all around wonderful provisioning system. I see the biggest advantage of Chef over its competitors, namely Puppet and Ansible (I don't have experience with any others), is the company and the community it facilitates. The most helpful part of the community is the wide, seemingly all inclusive, range of open source cookbooks available, which for the most part can be used out of the box to provision any system you might be building.

What do you dislike?

Developing new cookbooks—even more so when extending existing ones—for Chef requires a deep knowledge of how Chef works and of Ruby. Just knowing what you want to do is not enough.

Recommendations to others considering the product

If cookbooks exist for everything you need, use Berkshelf with Chef to provision your systems. If cookbooks do not exist for your purposes or you need finer grained control than what existing cookbooks provide, use a different tool. I highly recommend Ansible, having built Refinery29's provisioning system using it, and have mostly heard good things about Salt, but have yet to try it.

What business problems are you solving with the product? What benefits have you realized?

I used Chef at Elephant Ventures to build provisioning scripts for managing systems used to develop, and ocassionally deploy, web sites for our clients

Chef review by User in Retail
User in Retail
Validated Reviewer
Verified Current User
Review Source

"Best Configuration Management System"

What do you like best?

I have been working on Opscode Chef, though named is changed to Chef. I must say having worked on this technology for last 4 years now and also having worked on other configuration management system like puppet, anisble and salt. I always like chef for it's flexibility and easy to use features.

Chef does not imposes develoepers/devops to learn and understand any new platform, if some one can understand the basic of ruby, should be more then enough.

The community support is best part of the chef.

Documentation is the thing which you can rely on. There are many open source where it's documentation is not so good and supportive. Does not hold good with chef. Apart of official docs one can find many other posts on blogs on chef.

Over a period of time, chef has become a self sustained in pendent platform itself.

People of built tool of other tools to help many developers and devops.

What do you dislike?

Couple of tools which are out of the box, yet to see the stable release.

Recommendations to others considering the product

Considering the community support and the amount of the developer involved I can recommend others considering chef to other configure management system

What business problems are you solving with the product? What benefits have you realized?

I am running my entire e-commerce ERP and CRM solutions and running my entire aws stack using chef.

Chef review by Jared M. S.
Jared M. S.
Validated Reviewer
Review Source

"I use it for production technology at a cyber security startup and absolutely love it"

What do you like best?

I love the ease of use, specifically the short time required to get set up and start iterating on a project using chef to manage complex configurations across large clusters of servers.

What do you dislike?

There a few things I don't like, but one in particular is that when first learning chef I found it hard to find exactly what I needed in the documentation and tutorials. Eventually, however, I was able to dig through enough documentation that I found what I needed.

Recommendations to others considering the product

Rather than trying to parse through many tutorials, just get started on a project with it. You'll find that Chef's intuitive design makes this method of learning easy!

What business problems are you solving with the product? What benefits have you realized?

I am using Chef to automate configuration across many servers that require rapid iterations of changes to configuration. Without chef, I wouldn't be able to deploy changes to hundreds of machines spread across the world.

Chef review by Stewart H.
Stewart H.
Validated Reviewer
Verified Current User
Review Source

"A workhorse for deployment and configuration"

What do you like best?

The ability to manage multiple environments easily.

What do you dislike?

The domain specific language has a couple of small quirks.

Recommendations to others considering the product

https://docs.chef.io/ is your friend! The domain specific language (DSL) can be very hard at times especially for those coming from a non-Ruby programming back-ground.

What business problems are you solving with the product? What benefits have you realized?

We used this to manage all of the hosts configurations and applications that we deployed. It was used for all aspects to manage log locations, configurations, and even some kernel level configurations.

Chef review by Fábio S.
Fábio S.
Validated Reviewer
Review Source

"Infrastructure setup and maintenance automation for our PaaS offering"

What do you like best?

The powerful recipes system, version control and distributed capabilities. Chef allowed us to automate most, if not all the automated provisioning and change management systems in the underlying servers of our PaaS offering through Ruby scripting, shell scripting and Powershell scripting.

What do you dislike?

Ruby scripting. Ruby is a language that, in my opinion, is declining in relation to more straightforward ones like Python. Chef relies a lot in Ruby, which, in a company like ours, is a skill that is hard to find, and there are some features that are only found in external gems which have not been maintained for a while now.

Unfortunately the document is sparse and you'll have to comb through the internet to find answers to some common use cases.

Recommendations to others considering the product

Be proficient in Ruby. Understand the concepts behind it and go for a subscription that will help you get up and running quickly. Unfortunately the document is sparse and you'll have to comb through the internet to find answers to some common use cases.

What business problems are you solving with the product? What benefits have you realized?

Automation of the provisioning of our PaaS offering servers and change management (patch installation, platform upgrades, performance metering). Chef, as an open source solution backed by an Enterprise version, allowed us to start small and scale very quickly to around 600 servers now.

Chef review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"good work in setting up instance in cloud"

What do you like best?

After use the chef, it's easy and take very less time to set up a production instance(from 2 weeks to 3 hours). It's easy to learn by official docs.

What do you dislike?

a little expensive for side project / start up project

Recommendations to others considering the product

it's good enough when build a cloud environments. And it's a good option on migrating the existing biz to the cloud.

What business problems are you solving with the product? What benefits have you realized?

set up different environments(DEV/QA/PROD) by chef. Migrating the existing environment to the cloud and also build new environments.

Chef review by Administrator in Online Media
Administrator in Online Media
Validated Reviewer
Verified Current User
Review Source

"Best infrastructure as code tool!"

What do you like best?

The DSL is ruby based, it makes sense, and there is a vibrant community that is very helpful.

What do you dislike?

Initial setup can be a bit confusing. Chef-solo, chef-client, chef-zero, etc. Managing cookbooks is also confusing until you set up berkshelf, which is a third-party tool.

Recommendations to others considering the product

There are both free and paid options. Since chef 12, the enterprise and open source versions are very similar - but there are some paid options that are interesting, like analytics and chef delivery.

What business problems are you solving with the product? What benefits have you realized?

It solves the problem of having 'snowflake' servers - with Chef, every server is set up identically, which leads to a much more dependable environment. It also saves time when spinning up new machines.

Chef review by Consultant in Information Technology and Services
Consultant in Information Technology and Services
Validated Reviewer
Review Source

"Chef to automate your infra "

What do you like best?

Easy to understand, configure the management of your infrastructure

What do you dislike?

available documentation is less as compare to other tools,

Recommendations to others considering the product

Easy to learn, implement, configure, distribute over the landscape, Ruby is the main attraction, can cook the best food for you with its available cookbooks for your infrastructure to automate

What business problems are you solving with the product? What benefits have you realized?

we need to deploy a software developed by our developer, our infrastructure is very complex with different OS, environment, DBs, explorers, with the help of CHEF we did this within stipulated time without any issues.

Chef review by Administrator in Human Resources
Administrator in Human Resources
Validated Reviewer
Review Source

"Strong Core Software, Disappointing Community Additions"

What do you like best?

The diverse collection of community cookbooks.

What do you dislike?

The lack of maintenance on the majority of community cookbooks, which requires me to re-invent the wheel rather than use a pre-existing framework.

Recommendations to others considering the product

If you're new to configuration management ideas in general, Chef has a steep learning curve. The Chef software gives its admins just enough rope to hang themselves. If you're already familiar with the Chef DSL (or config management DSLs in general), Chef is a powerful tool.

What business problems are you solving with the product? What benefits have you realized?

Reproducible infrastructure. Chef is a great tool for infrastructure management, as long as you know what you're doing. Chef's documentation does not hand-hold users through its set-up, use, or troubleshooting so I've regularly relied on third-party blogs/instructions to maintain my Chef cookbooks. If you're looking for a tool that guides you through installation, configuration, and use, I recommend Puppet.

Chef review by Mohammad Hossein M.
Mohammad Hossein M.
Validated Reviewer
Review Source

"Simple yet Elegant"

What do you like best?

When you are a rapid web designer/developer, you never want to be late on delivery.

Chef should be your choice if you want to automate or config a system the way you want.

It's easier than what you might think.

Test it today!

What do you dislike?

I've never had a problem with Chef, so I do not dislike anything about it.

Recommendations to others considering the product

Just use it once and you'll love it.

What business problems are you solving with the product? What benefits have you realized?

1. Saving time,

2. Saving Money,

3. Saving Clients

4. Learn how to think big about my future web dev needs.

Chef review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Powerful but Quirky"

What do you like best?

* Keeps recipes in version control.

* Simple to modify system recipes

* Keeps systems in sync

What do you dislike?

* Can revert developer/administrator changes with little notice.

* Documentation can be out of date, suggesting commands that don't work with no clear suggestion for replacements.

* Individual node configuration is kept separate from recipes, not version controlled.

What business problems are you solving with the product? What benefits have you realized?

* Keeps a variety of servers maintained with proper configuration.

* Propagates changes to many servers simply.

* Makes transferring server roles between hardware much simpler.

Chef review by Earl W.
Earl W.
Validated Reviewer
Review Source

"Automation meets DevOps"

What do you like best?

It works on most platforms windows and Linux many flavors. Robust offering

What do you dislike?

Server head must be Linux. Not a bad thing.

Recommendations to others considering the product

A proven leader in Automation software

What business problems are you solving with the product? What benefits have you realized?

Server build similar to Desired State

Chef review by setu s.
setu s.
Validated Reviewer
Review Source

"Repeatable Infrastructure has been made easy"

What do you like best?

IT infrastructure can be saved /reused as when required. Less time to create infrastructure

What do you dislike?

Difficult to learn the language for beginners

What business problems are you solving with the product? What benefits have you realized?

1) Faster time to market

2) Less human error

3) Robust infrastrcuture

Chef review by User in Computer & Network Security
User in Computer & Network Security
Validated Reviewer
Verified Current User
Review Source

"Chef is Infraestructure as a Code"

What do you like best?

Not biased to said that everything from Opscode - Chef was well design, from their solo version to the Chef Provisioning module. You can write and deploy your whole infraestructure.

What do you dislike?

Chef Server Operation could give trouble as in performance issues.

Recommendations to others considering the product

Design well and do not forget to have clever metrics from your CI and CD workflow

What business problems are you solving with the product? What benefits have you realized?

Infraestructure as Code. Continuos Delivering and Integration.

Chef review by Almighty Y.
Almighty Y.
Validated Reviewer
Review Source

"Chef let IT infrastructure implementation like an art planting."

What do you like best?

1. Chef is cross platform management solution.

2. make automation easier.

3. Just like cooking, follow the menu instruct to make a delicious meal.

4. Node role define flexible, easy and good for work.

What do you dislike?

1. module enhance not easy.

2. knife tool function may be could more and more.

3. Could not direct access to node console.

4. System configuration were handle by admin node(chef server).

What business problems are you solving with the product? What benefits have you realized?

not yet.

Chef review by Justin S.
Justin S.
Validated Reviewer
Review Source

"The best of breed"

What do you like best?

100% open source

The right community and mindset

Jez Miller

Microsoft is partnering with chef and you'll see integrated TFS and visual studio stuff soon

Chef continuous deliver tool shows they know what they are doing

What do you dislike?

Nothing, the support is top notch. They are an awesome company that I fully recommend.

Recommendations to others considering the product

Stop looking here, puppet is just mimicking chef's model now...don't pick the company struggling to keep up.

What business problems are you solving with the product? What benefits have you realized?

Configuration as code

Configuration management

Continuous delivery

Infrastructure standup and tear down

Blue green deployments

Chef review by Paul B.
Paul B.
Validated Reviewer
Review Source

"Effective and smart way of config management, with a bit of a learning curve"

What do you like best?

Once you get running with Chef it's a very useful tool for config management, and a huge step forward over traditional methods.

What do you dislike?

The learning curve can be a bit steep, there is plenty of terminology and patterns to wrap your head around. Once it clicks though it's easy enough to use.

What business problems are you solving with the product? What benefits have you realized?

Used in the past to deploy and manage small - medium clusters.

Chef review by Sandip R.
Sandip R.
Validated Reviewer
Review Source

"Chef is one of best automation tool "

What do you like best?

We used chef configuration management is doing good job so faar.

What do you dislike?

Process of deployment configuration is something tricky to understand but once learned is one of the great tool

What business problems are you solving with the product? What benefits have you realized?

We have Internal product that we deploy on four different servers using chef and doing various configurations for each.

Chef review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Review Source

"Chef is just awesome"

What do you like best?

Because it's in Ruby and i love ruby.

Better Documentation

Platform support and use cases

Explicit dependency management

Esp rich marketplace of cookbooks

Chef Server management UI is awesome

What do you dislike?

Slow learning curve for beginners

Not as easy to pick up as YAML.

Knife Searching should be faster

Love to see setup more quicker

What business problems are you solving with the product? What benefits have you realized?

We use chef for configuration management.

There are lots of problem we solve using chef but we really enjoyed some of benefits from the tools

Berkshelf, Foodcritic, ChefSpec & Test Kitchen

Chef review by Administrator in Higher Education
Administrator in Higher Education
Validated Reviewer
Review Source

"Exective chef at a university "

What do you like best?

Being able to feed people with simpe ingrednts

What do you dislike?

At times the lack of knowdgle of the time it takes to make a dish

Recommendations to others considering the product

Not at this time

What business problems are you solving with the product? What benefits have you realized?

Meeting food cost

Kate from G2 Crowd

Learning about Chef?

I can help.
* We monitor all Chef reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.