Kubernetes vs. Docker Compose vs. Docker Swarm

Kubernetes is used for managing microclusters within our AWS infrastructure. This allows us to deploy new infrastructure in seconds.

Cluster chief orchestrator

Kubernetes was our go-to container managing tool.

I'm repeating myself. Look at ACS (Azure Container Services)

Container control plane

My main tool for container orchestration since 0.8

minor experience with kubernetes. helped a client setup a kubernetes infrastructure. love the elegance of the system.

Our servers are continuously deployed with Helm on a Kubernetes cluster running in AWS.

All 20+ micro-services that power Cirrus CI are orchestrated via Kubernetes.

Because it's really great and helps us do a lot of crazy stuff.

It's the glue that holds our container management together, allowing things to scale when and where we need them.

Easy to make TPU intensive projects , and scale them at the same time

Tumbo-Server is shipped as Docker images and Kubernetes does orchestation of worker's containers.

Our developer experience system is on Kubernetes (Google Kubernetes Engine at the moment). We would like to expand our Kubernetes clusters over other Kubernetes engine.

All dockerized services are deployed via Kube.

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