Docker Compose vs. Weave

Crating and linking Docker containers.

Since our production deployment makes use of the Convox platform, we use this to describe the containers to be deployed via Convox to AWS ECS.

We also use this for our local dev environment (previously used vagrant with chef).

test

We use docker compose to coordinate containers in out testing and stage environments.

Used in development

Web microservices.

Each python service runs in its own container, compose joins them together nicely.

Configure Docker container network.

Docker Compose is one of the pieces that really allows us to get new developers up and running quickly.

Simple container setup and orchestration

The core tech in ACS (Azure Container Services) we spin up a Kubernetes cluster and deploy our app into staging and production environments here.

Used Docker Compose during development for a number of more complex backend projects.

Docker Compose is just another part of my "infrastructure as code" initiative and allows me to build isolated pieces of systems with their own volumes and networks.

We use docker as a part of development environment

Docker Compose gives us an efficient and repeatable process for spinning up clusters of Docker containers. We actually use Docker Cloud.

Aside from our Minecraft-infrastructure, we compose it with ... Docker Compose! (kinda obious, eh .. ?) This includes for example the web-services, aswell as the monitoring and mail-infrastructure.

Only used to automate the development environment.

Simplifies setup of Docker local and production environments wonderfully.

Using Docker-compose for development

to build back-end applications using docker as easily as possible wether it's in development of production