Kubernetes vs Marathon

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

Kubernetes

59K
51K
+ 1
677
Marathon

84
91
+ 1
5
Add tool

Kubernetes vs Marathon: What are the differences?

Container Orchestration: Kubernetes vs. Marathon

Introduction

In modern software development, container orchestration plays a crucial role in managing and automating the deployment, scaling, and management of containers. Kubernetes and Marathon are two popular container orchestration platforms, each with its own unique features and capabilities. This comparison aims to highlight the key differences between Kubernetes and Marathon.

  1. Architecture: Kubernetes is built on a distributed architecture with a master-slave setup, where the master node manages and controls the cluster, while the worker nodes execute the tasks. On the other hand, Marathon follows a more centralized architecture, with a single Marathon instance managing the entire cluster.

  2. Scalability: Kubernetes is designed for massive scalability, with the ability to manage thousands of containers across multiple nodes. It offers features like automatic scaling, cluster-level scaling, and horizontal scaling to handle high loads. Marathon, while also scalable, may face limitations when managing large-scale deployments with thousands of containers.

  3. Flexibility: Kubernetes provides a highly flexible and extensible platform with a wide range of features and integrations. It supports various container runtimes, networking plugins, and storage options, allowing users to choose the components that best fit their requirements. Marathon, on the other hand, is more focused on running long-lived services and may be less flexible in terms of runtime options.

  4. Service Discovery and Networking: Kubernetes includes built-in service discovery and networking features, allowing containers within the cluster to easily communicate with each other. It provides a DNS-based service discovery mechanism and a powerful networking model. Marathon, while capable of integrating with external service discovery tools like Consul or ZooKeeper, doesn't have native service discovery and networking capabilities.

  5. Application Management: Kubernetes offers a rich set of features for managing complex applications and dependencies. It supports rolling updates, canary deployments, and blue-green deployments to ensure seamless application updates and zero-downtime deployments. Marathon, while capable of managing applications, may not provide the same level of sophistication and fine-grained control for complex application deployments.

  6. Community and Ecosystem: Kubernetes has a large, vibrant community and a robust ecosystem of tools, extensions, and third-party integrations. It benefits from the contributions of major cloud providers and has a wide range of resources and support available. Marathon, although actively maintained, may have a smaller community and ecosystem compared to Kubernetes.

In summary, Kubernetes and Marathon have different architectural approaches, scalability capabilities, flexibility, application management features, service discovery, and community support. The choice between the two depends on the specific requirements of the project, the complexity of the application, and the desired level of flexibility and scalability.

Advice on Kubernetes and Marathon

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
on
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 Kubernetes and Marathon
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 · | 30 upvotes · 9.6M 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Kubernetes
Pros of Marathon
  • 164
    Leading docker container management solution
  • 128
    Simple and powerful
  • 106
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Cheap
  • 8
    Simple
  • 6
    Self-healing
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Captain of Container Ship
  • 3
    A self healing environment with rich metadata
  • 3
    Runs on azure
  • 3
    Backed by Red Hat
  • 3
    Custom and extensibility
  • 2
    Sfg
  • 2
    Gke
  • 2
    Everything of CaaS
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable
  • 1
    High Availability
  • 1
    Powerful UI
  • 1
    Service Discovery
  • 1
    Load Balancing
  • 1
    Health Checks

Sign up to add or upvote prosMake informed product decisions

Cons of Kubernetes
Cons of Marathon
  • 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
  • 1
    Additional vendor lock-in (Docker)
  • 1
    More moving parts to secure
  • 1
    Additional Technology Overhead
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is 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.

    What is Marathon?

    Marathon is an Apache Mesos framework for container orchestration. Marathon provides a REST API for starting, stopping, and scaling applications. Marathon is written in Scala and can run in highly-available mode by running multiple copies. The state of running tasks gets stored in the Mesos state abstraction.

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

    What companies use Kubernetes?
    What companies use Marathon?
    See which teams inside your own company are using Kubernetes or Marathon.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Kubernetes?
    What tools integrate with Marathon?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Kubernetesetcd+2
    2
    1170
    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    2
    2373
    PythonDockerKubernetes+7
    3
    1110
    May 21 2020 at 12:02AM

    Rancher Labs

    KubernetesAmazon EC2Grafana+12
    5
    1500
    Apr 16 2020 at 5:34AM

    Rancher Labs

    KubernetesRancher+2
    2
    946
    What are some alternatives to Kubernetes and Marathon?
    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.
    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.
    OpenStack
    OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
    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.
    See all alternatives