Docker Swarm vs Kubernetes vs Rancher

Need advice about which tool to choose?Ask the StackShare community!

Docker Swarm

705
839
+ 1
267
Kubernetes

38.9K
33K
+ 1
628
Rancher

805
1.2K
+ 1
644
Advice on Docker Swarm, Kubernetes, and Rancher

Hello, we have a bunch of local hosts (Linux and Windows) where Docker containers are running with bamboo agents on them. Currently, each container is installed as a system service. Each host is set up manually. I want to improve the system by adding some sort of orchestration software that should install, update and check for consistency in my docker containers. I don't need any clouds, all hosts are local. I'd prefer simple solutions. What orchestration system should I choose?

See more
Replies (1)
Mortie Torabi
Recommends
Docker SwarmDocker Swarm

If you just want the basic orchestration between a set of defined hosts, go with Docker Swarm. If you want more advanced orchestration + flexibility in terms of resource management and load balancing go with Kubernetes. In both cases, you can make it even more complex while making the whole architecture more understandable and replicable by using Terraform.

See more
Decisions about Docker Swarm, Kubernetes, and Rancher
Michael Roberts

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%.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

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.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Docker Swarm
Pros of Kubernetes
Pros of Rancher
  • 54
    Docker friendly
  • 45
    Easy to setup
  • 39
    Standard Docker API
  • 37
    Easy to use
  • 22
    Native
  • 21
    Free
  • 12
    Clustering made easy
  • 11
    Simple usage
  • 10
    Integral part of docker
  • 5
    Cross Platform
  • 4
    Labels and annotations
  • 3
    Performance
  • 2
    Shallow learning curve
  • 2
    Easy Networking
  • 159
    Leading docker container management solution
  • 124
    Simple and powerful
  • 101
    Open source
  • 75
    Backed by google
  • 56
    The right abstractions
  • 24
    Scale services
  • 18
    Replication controller
  • 9
    Permission managment
  • 7
    Simple
  • 7
    Supports autoscaling
  • 6
    Cheap
  • 4
    Self-healing
  • 4
    Reliable
  • 4
    No cloud platform lock-in
  • 3
    Open, powerful, stable
  • 3
    Scalable
  • 3
    Quick cloud setup
  • 3
    Promotes modern/good infrascture practice
  • 2
    Backed by Red Hat
  • 2
    Runs on azure
  • 2
    Cloud Agnostic
  • 2
    Custom and extensibility
  • 2
    Captain of Container Ship
  • 2
    A self healing environment with rich metadata
  • 1
    Golang
  • 1
    Easy setup
  • 1
    Everything of CaaS
  • 1
    Sfg
  • 1
    Expandable
  • 1
    Gke
  • 103
    Easy to use
  • 79
    Open source and totally free
  • 63
    Multi-host docker-compose support
  • 58
    Load balancing and health check included
  • 58
    Simple
  • 44
    Rolling upgrades, green/blue upgrades feature
  • 42
    Dns and service discovery out-of-the-box
  • 37
    Only requires docker
  • 34
    Multitenant and permission management
  • 29
    Easy to use and feature rich
  • 11
    Cross cloud compatible
  • 11
    Does everything needed for a docker infrastructure
  • 8
    Simple and powerful
  • 8
    Next-gen platform
  • 7
    Very Docker-friendly
  • 6
    Support Kubernetes and Swarm
  • 6
    Application catalogs with stack templates (wizards)
  • 6
    Supports Apache Mesos, Docker Swarm, and Kubernetes
  • 6
    Rolling and blue/green upgrades deployments
  • 6
    High Availability service: keeps your app up 24/7
  • 5
    Easy to use service catalog
  • 4
    Very intuitive UI
  • 4
    IaaS-vendor independent, supports hybrid/multi-cloud
  • 4
    Awesome support
  • 3
    Scalable
  • 2
    Requires less infrastructure requirements

Sign up to add or upvote prosMake informed product decisions

Cons of Docker Swarm
Cons of Kubernetes
Cons of Rancher
  • 7
    Low adoption
  • 13
    Poor workflow for development
  • 11
    Steep learning curve
  • 5
    Orchestrates only infrastructure
  • 2
    High resource requirements for on-prem clusters
  • 8
    Hosting Rancher can be complicated

Sign up to add or upvote consMake informed product decisions