CoreOS vs Docker Swarm

Overview

CoreOS

Stacks217

Followers297

Votes44

Docker Swarm

Stacks779

Followers990

Votes282

CoreOS vs Docker Swarm: What are the differences?

CoreOS: Linux for Massive Server Deployments. CoreOS is designed for security, consistency, and reliability. Instead of installing packages via yum or apt, CoreOS uses Linux containers to manage your services at a higher level of abstraction. A single service's code and all dependencies are packaged within a container that can be run on one or many CoreOS machines; 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.

CoreOS and Docker Swarm are primarily classified as "Operating Systems" and "Container" tools respectively.

"Container management" is the primary reason why developers consider CoreOS over the competitors, whereas "Docker friendly" was stated as the key factor in picking Docker Swarm.

Docker Swarm is an open source tool with 5.63K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.

According to the StackShare community, Docker Swarm has a broader approval, being mentioned in 83 company stacks & 38 developers stacks; compared to CoreOS, which is listed in 45 company stacks and 12 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on CoreOS, Docker Swarm

Simon

Senior Fullstack Developer at QUANTUSflow Software GmbH

Apr 27, 2020

Decidedon

GitHub

GitHub Pages

Markdown

Our whole DevOps stack consists of the following tools:

@{GitHub}|tool:27| (incl. @{GitHub Pages}|tool:683|/@{Markdown}|tool:1147| for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
Respectively @{Git}|tool:1046| as revision control system
@{SourceTree}|tool:1599| as @{Git}|tool:1046| GUI
@{Visual Studio Code}|tool:4202| as IDE
@{CircleCI}|tool:190| for continuous integration (automatize development process)
@{Prettier}|tool:7035| / @{TSLint}|tool:5561| / @{ESLint}|tool:3337| as code linter
@{SonarQube}|tool:2638| as quality gate
@{Docker}|tool:586| as container management (incl. @{Docker Compose}|tool:3136| for multi-container application management)
@{VirtualBox}|tool:774| for operating system simulation tests
@{Kubernetes}|tool:1885| as cluster management for docker containers
@{Heroku}|tool:133| for deploying in test environments
@{nginx}|tool:1052| as web server (preferably used as facade server in production environment)
@{SSLMate}|tool:2752| (using @{OpenSSL}|tool:3091|) for certificate management
@{Amazon EC2}|tool:18| (incl. @{Amazon S3}|tool:25|) for deploying in stage (production-like) and production environments
@{PostgreSQL}|tool:1028| as preferred database system
@{Redis}|tool:1031| 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.

12.8M views12.8M

Comments

Detailed Comparison

CoreOS	Docker Swarm
It is designed for security, consistency, and reliability. Instead of installing packages via yum or apt, it uses Linux containers to manage your services at a higher level of abstraction. A single service's code and all dependencies are packaged within a container that can be run on one or many machines.	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.
Great to develop; Test; Operate	-
Statistics
Stacks 217	Stacks 779
Followers 297	Followers 990
Votes 44	Votes 282
Pros & Cons
Pros 20 Container management 15 Lightweight 9 Systemd Cons 3 End-of-lifed	Pros 55 Docker friendly 46 Easy to setup 40 Standard Docker API 38 Easy to use 23 Native Cons 9 Low adoption
Integrations
No integrations available	Docker

What are some alternatives to CoreOS, Docker Swarm?

Kubernetes

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Rancher

Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.

Docker Compose

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.

Ubuntu

Ubuntu is an ancient African word meaning ‘humanity to others’. It also means ‘I am what I am because of who we all are’. The Ubuntu operating system brings the spirit of Ubuntu to the world of computers.

Tutum

Tutum lets developers easily manage and run lightweight, portable, self-sufficient containers from any application. AWS-like control, Heroku-like ease. The same container that a developer builds and tests on a laptop can run at scale in Tutum.

Debian

Debian systems currently use the Linux kernel or the FreeBSD kernel. Linux is a piece of software started by Linus Torvalds and supported by thousands of programmers worldwide. FreeBSD is an operating system including a kernel and other software.

Portainer

It is a universal container management tool. It works with Kubernetes, Docker, Docker Swarm and Azure ACI. It allows you to manage containers without needing to know platform-specific code.

Arch Linux

A lightweight and flexible Linux distribution that tries to Keep It Simple.

Fedora

Fedora is a Linux-based operating system that provides users with access to the latest free and open source software, in a stable, secure and easy to manage form. Fedora is the largest of many free software creations of the Fedora Project. Because of its predominance, the word "Fedora" is often used interchangeably to mean both the Fedora Project and the Fedora operating system.

Linux Mint

The purpose of Linux Mint is to produce a modern, elegant and comfortable operating system which is both powerful and easy to use.

Related Comparisons

@{GitHub}|tool:27| (incl. @{GitHub Pages}|tool:683|/@{Markdown}|tool:1147| for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
Respectively @{Git}|tool:1046| as revision control system
@{SourceTree}|tool:1599| as @{Git}|tool:1046| GUI
@{Visual Studio Code}|tool:4202| as IDE
@{CircleCI}|tool:190| for continuous integration (automatize development process)
@{Prettier}|tool:7035| / @{TSLint}|tool:5561| / @{ESLint}|tool:3337| as code linter
@{SonarQube}|tool:2638| as quality gate
@{Docker}|tool:586| as container management (incl. @{Docker Compose}|tool:3136| for multi-container application management)
@{VirtualBox}|tool:774| for operating system simulation tests
@{Kubernetes}|tool:1885| as cluster management for docker containers
@{Heroku}|tool:133| for deploying in test environments
@{nginx}|tool:1052| as web server (preferably used as facade server in production environment)
@{SSLMate}|tool:2752| (using @{OpenSSL}|tool:3091|) for certificate management
@{Amazon EC2}|tool:18| (incl. @{Amazon S3}|tool:25|) for deploying in stage (production-like) and production environments
@{PostgreSQL}|tool:1028| as preferred database system
@{Redis}|tool:1031| 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.

CoreOS vs Docker Swarm