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.
What is Docker Compose?
What is Weave?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Docker Compose?
Why do developers choose Weave?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Docker Compose?
What are the cons of using Weave?
What companies use Weave?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Docker Compose?
What tools integrate with Weave?
Sign up to get full access to all the tool integrationsMake informed product decisions
Fresha Engineering
Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.
Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.
We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.
Docker ComposeSince 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).
Docker ComposeAside 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.
Docker ComposeDocker 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.
Docker ComposeOur application will consist of several containers each communicating with each other. Using docker-compose, we can orchestrate several containers at once.
Docker ComposeThe core tech in ACS (Azure Container Services) we spin up a Kubernetes cluster and deploy our app into staging and production environments here.