Need advice about which tool to choose?Ask the StackShare community!
Composer vs Docker Swarm: What are the differences?
What is Composer? Dependency Manager for PHP. Composer is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you.
What is Docker Swarm? Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
Composer belongs to "Package Managers" category of the tech stack, while Docker Swarm can be primarily classified under "Container Tools".
"Must have dependency manager for PHP" is the top reason why over 3 developers like Composer, while over 44 developers mention "Docker friendly" as the leading cause for choosing Docker Swarm.
Composer and Docker Swarm are both open source tools. Composer with 20.5K GitHub stars and 5.56K forks on GitHub appears to be more popular than Docker Swarm with 5.64K GitHub stars and 1.12K GitHub forks.
According to the StackShare community, Docker Swarm has a broader approval, being mentioned in 117 company stacks & 267 developers stacks; compared to Composer, which is listed in 138 company stacks and 246 developer stacks.
Our whole DevOps stack consists of the following tools:
- GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
- Respectively Git as revision control system
- SourceTree as Git GUI
- Visual Studio Code as IDE
- CircleCI for continuous integration (automatize development process)
- Prettier / TSLint / ESLint as code linter
- SonarQube as quality gate
- Docker as container management (incl. Docker Compose for multi-container application management)
- VirtualBox for operating system simulation tests
- Kubernetes as cluster management for docker containers
- Heroku for deploying in test environments
- nginx as web server (preferably used as facade server in production environment)
- SSLMate (using OpenSSL) for certificate management
- Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
- PostgreSQL as preferred database system
- Redis as preferred in-memory database/store (great for caching)
The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:
- Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
- Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
- Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
- Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
- Scalability: All-in-one framework for distributed systems.
- Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
Pros of Composer
- Must have dependency manager for PHP7
- Centralized autoload.php3
- Large number of libraries3
Pros of Docker Swarm
- Docker friendly55
- Easy to setup46
- Standard Docker API40
- Easy to use38
- Native23
- Free22
- Clustering made easy13
- Simple usage12
- Integral part of docker11
- Cross Platform6
- Labels and annotations5
- Performance5
- Easy Networking3
- Shallow learning curve3
Sign up to add or upvote prosMake informed product decisions
Cons of Composer
Cons of Docker Swarm
- Low adoption9