Chef vs Puppet Labs: What are the differences?
Developers describe Chef as "Build, destroy and rebuild servers on any public or private cloud". Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others. On the other hand, Puppet Labs is detailed as "Server automation framework and application". Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Chef and Puppet Labs can be categorized as "Server Configuration and Automation" tools.
Some of the features offered by Chef are:
- Access to 800+ Reusable Cookbooks
- Integration with Leading Cloud Providers
- Enterprise Platform Support including Windows and Solaris
On the other hand, Puppet Labs provides the following key features:
- Insight- Puppet Enterprise's event inspector gives immediate and actionable insight into your environment, showing you what changed, where and how by classes, nodes and resources.
- Discovery- Puppet Enterprise delivers a dynamic and fully-pluggable discovery service that allows you to take advantage of any data source or real-time query results to quickly locate, identify and group cloud nodes.
- Provisioning- Automatically provision and configure bare metal, virtual, and private or public cloud capacity, all from a single pane. Save time getting your cloud projects off the ground by reusing the same configuration modules you set up for your physical deployments.
"Dynamic and idempotent server configuration" is the top reason why over 104 developers like Chef, while over 45 developers mention "Devops" as the leading cause for choosing Puppet Labs.
Chef and Puppet Labs are both open source tools. It seems that Chef with 5.85K GitHub stars and 2.36K forks on GitHub has more adoption than Puppet Labs with 5.37K GitHub stars and 2.1K GitHub forks.
Airbnb, Facebook, and Slack are some of the popular companies that use Chef, whereas Puppet Labs is used by Uber Technologies, Twitch, and PayPal. Chef has a broader approval, being mentioned in 360 company stacks & 80 developers stacks; compared to Puppet Labs, which is listed in 180 company stacks and 49 developer stacks.
What is Chef?
What is Puppet Labs?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Chef?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I'm using puppet to configure my servers. This makes it really simple to ensure that I have the same environment. There is a bit of a learning curve, but the repeatability definitely makes it worth the effort. I found puppet to be a little easier to pick up relative to chef, but I've used both. They're both great solutions.
I really like that there are a lot of modules available on the puppet forge that are being actively maintained.
We provision all servers with puppet. We have one central Puppet server which uses puppet modules referenced by a Puppetfile. Those puppet modules are partly from forge and partly self written.
All modules which are self written, have to be tested using rspec-puppet and beaker.
Out custom recipes makes it simple for developers bootstrap process (using vagrant) and that same recipe is also the one that is used to prep instances
Opstax uses puppet for role/profile based configuration management and the distribution of small/static code.
Configures or servers and allows us to be region independent we have 5 regions across the globe.