Overview

Kubernetes

Stacks61.2K

Followers52.8K

Votes685

Moby

Stacks36

Followers57

Votes0

GitHub Stars71.0K

Forks18.8K

Kubernetes vs Moby: What are the differences?

Introduction

In the world of containerization and managing containers at scale, two popular technologies that are often compared are Kubernetes and Moby. While both serve different purposes, there are key differences between them that distinguish their functionalities and use cases.

Architecture: Kubernetes is an open-source container orchestration platform that provides a framework for automating the deployment, scaling, and management of containerized applications. It uses a master-worker architecture where a cluster consists of a master node responsible for managing the cluster and worker nodes that run the containers. On the other hand, Moby is an open-source project that serves as the upstream for Docker. It's a modular framework for building customized container systems and can be seen as a building block for Docker, offering greater flexibility in the container stack.
Scalability: Kubernetes is highly scalable and allows you to easily scale the number of containers running in a cluster horizontally. It can handle large-scale deployments with thousands of containers efficiently. Moby, on the other hand, does not provide native scaling features. Its focus is more on customization and building container systems rather than managing large-scale deployments.
Ease of Use: Kubernetes has a steep learning curve and requires a good understanding of its concepts and components to use it effectively. It provides complex abstractions and a rich set of features for managing containers at scale. Moby, on the other hand, aims to provide a simplified experience for developers and allows for more straightforward customization of container systems. It offers a lighter and more accessible approach to containerization.
Community and Support: Kubernetes has a massive and vibrant community behind it, with contributions from major tech companies and a wide range of tools and plugins available. It has become the de facto standard for container orchestration. Moby, being the upstream for Docker, also benefits from a strong community and support. However, the focus of their communities differs, with Kubernetes focusing more on large-scale deployments and Moby on building customized container systems.
Use Case: Kubernetes is designed to handle complex container orchestration scenarios, making it suitable for large-scale production deployments. It provides built-in features for load balancing, service discovery, and self-healing. Moby, on the other hand, is more geared towards developers and individuals who want to customize their container systems or build their own container-related projects.
Containerization Stack: Kubernetes provides a higher-level abstraction for managing containers and can work with various container runtimes, including Docker, containerd, and CRI-O. It focuses on the orchestration layer and provides features like scaling, service discovery, and rolling updates. Moby, being the upstream for Docker, focuses on the lower-level container runtime, allowing users to build their own container systems using components like containerd or runC.

In summary, Kubernetes is a powerful container orchestration platform designed for large-scale deployments, while Moby serves as a modular building block for Docker and offers more customization options for container systems.

🔥 Trending in Container Registry on StackShare

SpinKube Container Registry

Hyper-efficient serverless on Kubernetes, powered by WebAssembly

Try it View Docs Alternatives

Try

Advice on Kubernetes, Moby

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

Michael

CEO at asencis Ltd

Jan 5, 2021

Needs advice

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

272k views272k

Comments

Detailed Comparison

Kubernetes	Moby
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.	Moby is a project which provides a “Lego set” of dozens of components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts to experiment and exchange ideas. Docker the product will be assembled from components that are packaged by the Moby project.
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	Orchestration; Image Management; Secret Management; Configuration Management; Networking; Provisioning
Statistics
GitHub Stars -	GitHub Stars 71.0K
GitHub Forks -	GitHub Forks 18.8K
Stacks 61.2K	Stacks 36
Followers 52.8K	Followers 57
Votes 685	Votes 0
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	No community feedback yet
Integrations
Vagrant Docker Rackspace Cloud Servers Microsoft Azure Google Compute Engine Ansible Google Kubernetes Engine	Docker

What are some alternatives to Kubernetes, Moby?

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.

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.

Flocker

Flocker is a data volume manager and multi-host Docker cluster management tool. With it you can control your data using the same tools you use for your stateless applications. This means that you can run your databases, queues and key-value stores in Docker and move them around as easily as the rest of your app.