Need advice about which tool to choose?Ask the StackShare community!
Docker Compose vs Weave: 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, Weave is detailed as "Weave creates a virtual network that connects Docker containers deployed across multiple hosts". Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.
Docker Compose and Weave belong to "Container Tools" category of the tech stack.
"Multi-container descriptor" is the primary reason why developers consider Docker Compose over the competitors, whereas "Easy setup" was stated as the key factor in picking Weave.
Docker Compose and Weave are both open source tools. It seems that Docker Compose with 16.6K GitHub stars and 2.56K forks on GitHub has more adoption than Weave with 5.57K GitHub stars and 517 GitHub forks.
StackShare, CircleCI, and Docker are some of the popular companies that use Docker Compose, whereas Weave is used by Excursiopedia, Tutum, and PlanetPass. Docker Compose has a broader approval, being mentioned in 795 company stacks & 625 developers stacks; compared to Weave, which is listed in 11 company stacks and 4 developer stacks.
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%.