Need advice about which tool to choose?Ask the StackShare community!

Docker Compose

12.7K
9.1K
+ 1
471
Terraform

8.9K
6.8K
+ 1
294
Add tool

Docker Compose vs Terraform: What are the differences?

Developers describe Docker Compose as "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. On the other hand, Terraform is detailed as "Describe your complete infrastructure as code and build resources across providers". With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Docker Compose and Terraform are primarily classified as "Container" and "Infrastructure Build" tools respectively.

"Multi-container descriptor" is the top reason why over 111 developers like Docker Compose, while over 80 developers mention "Infrastructure as code" as the leading cause for choosing Terraform.

Docker Compose and Terraform are both open source tools. Terraform with 17.4K GitHub stars and 4.77K forks on GitHub appears to be more popular than Docker Compose with 16.4K GitHub stars and 2.52K GitHub forks.

StackShare, hike, and Harvest are some of the popular companies that use Docker Compose, whereas Terraform is used by Instacart, Slack, and Twitch. Docker Compose has a broader approval, being mentioned in 787 company stacks & 608 developers stacks; compared to Terraform, which is listed in 490 company stacks and 298 developer stacks.

Decisions about Docker Compose and Terraform

Because Pulumi uses real programming languages, you can actually write abstractions for your infrastructure code, which is incredibly empowering. You still 'describe' your desired state, but by having a programming language at your fingers, you can factor out patterns, and package it up for easier consumption.

See more
Sergey Ivanov
Overview

We use Terraform to manage AWS cloud environment for the project. It is pretty complex, largely static, security-focused, and constantly evolving.

Terraform provides descriptive (declarative) way of defining the target configuration, where it can work out the dependencies between configuration elements and apply differences without re-provisioning the entire cloud stack.

Advantages

Terraform is vendor-neutral in a way that it is using a common configuration language (HCL) with plugins (providers) for multiple cloud and service providers.

Terraform keeps track of the previous state of the deployment and applies incremental changes, resulting in faster deployment times.

Terraform allows us to share reusable modules between projects. We have built an impressive library of modules internally, which makes it very easy to assemble a new project from pre-fabricated building blocks.

Disadvantages

Software is imperfect, and Terraform is no exception. Occasionally we hit annoying bugs that we have to work around. The interaction with any underlying APIs is encapsulated inside 3rd party Terraform providers, and any bug fixes or new features require a provider release. Some providers have very poor coverage of the underlying APIs.

Terraform is not great for managing highly dynamic parts of cloud environments. That part is better delegated to other tools or scripts.

Terraform state may go out of sync with the target environment or with the source configuration, which often results in painful reconciliation.

See more

I personally am not a huge fan of vendor lock in for multiple reasons:

  • I've seen cost saving moves to the cloud end up costing a fortune and trapping companies due to over utilization of cloud specific features.
  • I've seen S3 failures nearly take down half the internet.
  • I've seen companies get stuck in the cloud because they aren't built cloud agnostic.

I choose to use terraform for my cloud provisioning for these reasons:

  • It's cloud agnostic so I can use it no matter where I am.
  • It isn't difficult to use and uses a relatively easy to read language.
  • It tests infrastructure before running it, and enables me to see and keep changes up to date.
  • It runs from the same CLI I do most of my CM work from.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Docker Compose
Pros of Terraform
  • 118
    Multi-container descriptor
  • 107
    Fast development environment setup
  • 75
    Easy linking of containers
  • 65
    Simple yaml configuration
  • 58
    Easy setup
  • 15
    Yml or yaml format
  • 11
    Use Standard Docker API
  • 7
    Open source
  • 4
    Can choose Discovery Backend
  • 4
    Go from template to application in minutes
  • 2
    Scalable
  • 2
    Easy configuration
  • 2
    Kubernetes integration
  • 1
    Quick and easy
  • 101
    Infrastructure as code
  • 68
    Declarative syntax
  • 43
    Planning
  • 26
    Simple
  • 23
    Parallelism
  • 6
    Cloud agnostic
  • 5
    It's like coding your infrastructure in simple English
  • 4
    Well-documented
  • 3
    Automates infrastructure deployments
  • 3
    Platform agnostic
  • 3
    Immutable infrastructure
  • 2
    Automation
  • 2
    Portability
  • 2
    Scales to hundreds of hosts
  • 2
    Extendable
  • 1
    Lightweight

Sign up to add or upvote prosMake informed product decisions

Cons of Docker Compose
Cons of Terraform
  • 7
    Tied to single machine
  • 4
    Still very volatile, changing syntax often
  • 1
    Doesn't have full support to GKE

Sign up to add or upvote consMake informed product decisions

What is Docker Compose?

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.

What is Terraform?

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Docker Compose?
What companies use Terraform?
See which teams inside your own company are using Docker Compose or Terraform.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Docker Compose?
What tools integrate with Terraform?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

GitHubPythonNode.js+47
45
68151
GitHubPythonGit+22
17
13130
JavaScriptGitHubjQuery+26
18
4535
JavaScriptGitHubPython+42
52
19407
What are some alternatives to Docker Compose and Terraform?
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Docker
The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
Docker Swarm
Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
Helm
Helm is the best way to find, share, and use software built for Kubernetes.
Ansible
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
See all alternatives
Interest over time