Chef vs Google Cloud Deployment Manager: 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, Google Cloud Deployment Manager is detailed as "Create and manage cloud resources with simple templates". Google Cloud Deployment Manager allows you to specify all the resources needed for your application in a declarative format using yaml.
Chef can be classified as a tool in the "Server Configuration and Automation" category, while Google Cloud Deployment Manager is grouped under "Infrastructure Build Tools".
Chef is an open source tool with 5.86K GitHub stars and 2.36K GitHub forks. Here's a link to Chef's open source repository on GitHub.
What is Chef?
What is Google Cloud Deployment Manager?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Google Cloud Deployment Manager?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Chef?
What are the cons of using Google Cloud Deployment Manager?
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
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