DC/OS vs Kubernetes

Overview

Kubernetes

Stacks61.2K

Followers52.8K

Votes685

DC/OS

Stacks109

Followers180

Votes12

GitHub Stars2.4K

Forks488

DC/OS vs Kubernetes: What are the differences?

Introduction

DC/OS (Distributed Cloud Operating System) and Kubernetes are both popular container orchestration platforms used to manage and deploy applications at scale. While both platforms share similarities in their ability to automate container operations, there are key differences that set them apart.

Architecture: DC/OS is built on a distributed system architecture, providing a unified platform for deploying and managing services across multiple nodes in a cluster. Kubernetes, on the other hand, follows a master-worker architecture, where the master node manages the cluster and assigns tasks to worker nodes. This architectural difference can impact the scalability and fault tolerance capabilities of each platform.
Ecosystem: DC/OS offers an integrated ecosystem of services, including a package manager for simplified software installation and a rich set of built-in tools. Kubernetes, on the other hand, focuses on providing a flexible platform with a wide range of plugins and extensions that can be integrated into the ecosystem. The choice between the two platforms depends on the specific requirements and preferences of the users.
Networking: DC/OS uses its own proprietary network overlay technology called Virtual Network System (VNS), which allows for seamless communication between containerized applications. Kubernetes, on the other hand, relies on software-defined networking (SDN) solutions like Calico or Flannel to provide network connectivity between containers. The choice of networking solution can impact the performance and security of container communication.
Community support: Kubernetes has a large and active community of contributors and users, which has led to a significant growth in its ecosystem and availability of resources. DC/OS, although also supported by a community, may have a smaller user base and a more limited set of resources compared to Kubernetes. Consideration should be given to the availability of support and resources when choosing between the two platforms.
Application focus: DC/OS is designed to support a wide range of applications, including both stateless and stateful workloads, and provides features like persistent storage and multi-tenancy. Kubernetes, on the other hand, is primarily focused on stateless applications and provides features like auto-scaling and self-healing for application deployment. The application focus of each platform should align with the specific needs of the workload being deployed.

In summary, DC/OS and Kubernetes are both powerful container orchestration platforms with different architectural approaches, ecosystem offerings, networking options, community support, and application focuses. The choice between the two depends on factors such as desired architecture, available resources, networking requirements, and the nature of the applications being deployed.

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 Kubernetes, DC/OS

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

Anis

Founder at Odix

Nov 7, 2020

Review

I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).

You pay less money, but u need some technical 2 - 3 guys to make that done.

Good luck

115k views115k

Comments

Detailed Comparison

Kubernetes	DC/OS
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.	Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.
Lightweight, simple and accessible;Built for a multi-cloud world, public, private or hybrid;Highly modular, designed so that all of its components are easily swappable	High Resource Utilization;Mixed Workload Colocation;Container Orchestration;Resource Isolation;Stateful Storage;Package Repositories;Public Cloud;Private Cloud;On-Premise;Command Line Interface;Web Interface;Elastic Scalability;High Availability;Zero Downtime Upgrades;Service Discovery;Load Balancing;Production-Ready
Statistics
GitHub Stars -	GitHub Stars 2.4K
GitHub Forks -	GitHub Forks 488
Stacks 61.2K	Stacks 109
Followers 52.8K	Followers 180
Votes 685	Votes 12
Pros & Cons
Pros 166 Leading docker container management solution 130 Simple and powerful 108 Open source 76 Backed by google 58 The right abstractions Cons 16 Steep learning curve 15 Poor workflow for development 8 Orchestrates only infrastructure 4 High resource requirements for on-prem clusters 2 Too heavy for simple systems	Pros 5 Easy to setup a HA cluster 3 Open source 2 Has templates to install via AWS and Azure 1 Easy to get services running and operate them 1 Easy Setup
Integrations
Vagrant Docker Rackspace Cloud Servers Microsoft Azure Google Compute Engine Ansible Google Kubernetes Engine	Apache Mesos

What are some alternatives to Kubernetes, DC/OS?

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.

Docker Swarm

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.

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.

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.

Codefresh

Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines.

Nomad

Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.

Apache Mesos

Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.

CAST.AI

It is an AI-driven cloud optimization platform for Kubernetes. Instantly cut your cloud bill, prevent downtime, and 10X the power of DevOps.

k3s

Certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances. Supports something as small as a Raspberry Pi or as large as an AWS a1.4xlarge 32GiB server.

Related Comparisons

DC/OS vs Kubernetes: What are the differences?

Introduction

Architecture: DC/OS is built on a distributed system architecture, providing a unified platform for deploying and managing services across multiple nodes in a cluster. Kubernetes, on the other hand, follows a master-worker architecture, where the master node manages the cluster and assigns tasks to worker nodes. This architectural difference can impact the scalability and fault tolerance capabilities of each platform.
Ecosystem: DC/OS offers an integrated ecosystem of services, including a package manager for simplified software installation and a rich set of built-in tools. Kubernetes, on the other hand, focuses on providing a flexible platform with a wide range of plugins and extensions that can be integrated into the ecosystem. The choice between the two platforms depends on the specific requirements and preferences of the users.
Networking: DC/OS uses its own proprietary network overlay technology called Virtual Network System (VNS), which allows for seamless communication between containerized applications. Kubernetes, on the other hand, relies on software-defined networking (SDN) solutions like Calico or Flannel to provide network connectivity between containers. The choice of networking solution can impact the performance and security of container communication.
Community support: Kubernetes has a large and active community of contributors and users, which has led to a significant growth in its ecosystem and availability of resources. DC/OS, although also supported by a community, may have a smaller user base and a more limited set of resources compared to Kubernetes. Consideration should be given to the availability of support and resources when choosing between the two platforms.
Application focus: DC/OS is designed to support a wide range of applications, including both stateless and stateful workloads, and provides features like persistent storage and multi-tenancy. Kubernetes, on the other hand, is primarily focused on stateless applications and provides features like auto-scaling and self-healing for application deployment. The application focus of each platform should align with the specific needs of the workload being deployed.

DC/OS vs Kubernetes

Overview

DC/OS vs Kubernetes: What are the differences?