Need advice about which tool to choose?Ask the StackShare community!
Kubernetes vs Tutum: What are the differences?
Developers describe Kubernetes as "Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops". 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. On the other hand, Tutum is detailed as "Build, deploy, monitor, and scale Docker containers". 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.
Kubernetes and Tutum can be primarily classified as "Container" tools.
Some of the features offered by Kubernetes are:
- 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
On the other hand, Tutum provides the following key features:
- Deploy from Docker Hub
- Free private Docker registry
- CLI Tool
"Leading docker container management solution" is the top reason why over 134 developers like Kubernetes, while over 34 developers mention "Awesome user interface" as the leading cause for choosing Tutum.
Kubernetes is an open source tool with 55.1K GitHub stars and 19.1K GitHub forks. Here's a link to Kubernetes's open source repository on GitHub.
According to the StackShare community, Kubernetes has a broader approval, being mentioned in 1048 company stacks & 1099 developers stacks; compared to Tutum, which is listed in 11 company stacks and 4 developer stacks.
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.
Pros of Kubernetes
- Leading docker container management solution166
- Simple and powerful129
- Open source107
- Backed by google76
- The right abstractions58
- Scale services25
- Replication controller20
- Permission managment11
- Supports autoscaling9
- Simple8
- Cheap8
- Self-healing6
- Open, powerful, stable5
- Reliable5
- No cloud platform lock-in5
- Promotes modern/good infrascture practice5
- Scalable4
- Quick cloud setup4
- Custom and extensibility3
- Captain of Container Ship3
- Cloud Agnostic3
- Backed by Red Hat3
- Runs on azure3
- A self healing environment with rich metadata3
- Everything of CaaS2
- Gke2
- Golang2
- Easy setup2
- Expandable2
- Sfg2
Pros of Tutum
- Awesome user interface35
- Free private docker registry28
- Its super easy24
- Docker public index integration24
- Friendly support21
- I could bring my own node20
- Load balancing19
- Easy to use Jumpstart Images14
- High resilience12
- Love the tutum images for php & mysql12
- Makes code delivery super easy5
- Free5
- Cross cloud platform5
- Iteratively and continuous growth3
- Documentation2
- High level and minimalist2
- Tutum Buttons - 1-click deploy1
- On demand environment1
- Closing Down :(1
- Free low TTL (60s) DNS service1
Sign up to add or upvote prosMake informed product decisions
Cons of Kubernetes
- Steep learning curve16
- Poor workflow for development15
- Orchestrates only infrastructure8
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional vendor lock-in (Docker)1
- More moving parts to secure1
- Additional Technology Overhead1
Cons of Tutum
Sign up to add or upvote consMake informed product decisions
What is Kubernetes?
What is Tutum?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kubernetes?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+1
+2
+9
+11
+11+7
+12
+2