[webo]

Our team is <15 engineers. The set up is roughly as below. We have around 40 services. Ping me if you wanna talk more.

https://cloudcraft.co/view/5582ddd4-c6f8-4354-8f5b-9fb0a3744...

* Development: docker + docker-compose. Ideally, we would want to get rid of docker-compose for development.

* CI: Travis (planning on switching to something that is more on the CD side)

* Infrastructure management: terraform

* Prod: AWS, CoreOs, Kubernetes 1 master node and 5-6 worker nodes (m4.large) in an autoscaling group.

Infrastructure deployments and updates are done by Terraform. Blue/Green deployments thanks to the autoscaling group.

Kubernetes deployments and updates are done by kubectl.

There's still problems with each piece, but for the most part they work great without much trouble.

[lifty]

If you want to get rid of docker-compose, you could try using minikube (https://github.com/kubernetes/minikube), which is a local Kubernetes deployment, similar to the desktop version of Docker. It works well and supports all major platforms.

[sandGorgon]

docker 1.13 swarm has full compatiblity to use compose file format to launch a cluster. you should try that. https://www.infoq.com/news/2017/01/docker-1.13

[webo]

In my experience, docker itself is not very stable, and swarm is nowhere close to Kubernetes offers.