Need advice about which tool to choose?Ask the StackShare community!
Chef vs Docker Compose: What are the differences?
What is Chef? 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.
What is Docker Compose? Define and run multi-container applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
Chef can be classified as a tool in the "Server Configuration and Automation" category, while Docker Compose is grouped under "Container Tools".
"Dynamic and idempotent server configuration" is the top reason why over 104 developers like Chef, while over 111 developers mention "Multi-container descriptor" as the leading cause for choosing Docker Compose.
Chef and Docker Compose are both open source tools. Docker Compose with 16.4K GitHub stars and 2.52K forks on GitHub appears to be more popular than Chef with 5.83K GitHub stars and 2.35K GitHub forks.
According to the StackShare community, Docker Compose has a broader approval, being mentioned in 787 company stacks & 608 developers stacks; compared to Chef, which is listed in 359 company stacks and 80 developer stacks.
I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)
I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.
The most important factors for me are simplicity, ease of use, shortest learning curve.
I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.
The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.
If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate
We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.
Pros of Chef
- Dynamic and idempotent server configuration110
- Reusable components76
- Integration testing with Vagrant47
- Repeatable43
- Mock testing with Chefspec30
- Ruby14
- Can package cookbooks to guarantee repeatability8
- Works with AWS7
- Has marketplace where you get readymade cookbooks3
- Matured product with good community support3
- Less declarative more procedural2
- Open source configuration mgmt made easy(ish)2
Pros of Docker Compose
- Multi-container descriptor123
- Fast development environment setup110
- Easy linking of containers79
- Simple yaml configuration68
- Easy setup60
- Yml or yaml format16
- Use Standard Docker API12
- Open source8
- Go from template to application in minutes5
- Can choose Discovery Backend5
- Scalable4
- Easy configuration4
- Kubernetes integration4
- Quick and easy3
Sign up to add or upvote prosMake informed product decisions
Cons of Chef
Cons of Docker Compose
- Tied to single machine9
- Still very volatile, changing syntax often5
Sign up to add or upvote consMake informed product decisions
What is Chef?
What is Docker Compose?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Docker Compose?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Chef?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+47+46
+26+42+26
+27
+39