Need advice about which tool to choose?Ask the StackShare community!
Kubernetes vs Titus: What are the differences?
What is Kubernetes? 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.
What is Titus? A container management platform by Netflix. Titus is a container management platform that provides scalable and reliable container execution and cloud-native integration with Amazon AWS. Titus was built internally at Netflix and is used in production to power Netflix streaming, recommendation, and content systems.
Kubernetes and Titus 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, Titus provides the following key features:
- A production ready container platform - Titus is run in production at Netflix, managing thousands of AWS EC2 instances and launching hundreds of thousands of containers daily for both batch and service workloads.
- Cloud-native integrations with AWS - Titus integrates with AWS services, such as VPC networking, IAM and Security Group concepts, Application Load Balancing, and EC2 capacity management. These integrations enable many cloud services to work seamlessly with containers.
- Netflix OSS integration - Titus works natively with many existing Netflix OSS projects, including Spinnaker, Eureka, Archaius, and Atlas among others.
Kubernetes and Titus are both open source tools. It seems that Kubernetes with 55K GitHub stars and 19.1K forks on GitHub has more adoption than Titus with 1.83K GitHub stars and 97 GitHub forks.
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?
Docker SwarmIf 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.
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%.
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 solution161
- Simple and powerful126
- Open source103
- Backed by google75
- The right abstractions56
- Scale services24
- Replication controller19
- Permission managment9
- Simple7
- Supports autoscaling7
- Cheap6
- Self-healing4
- No cloud platform lock-in4
- Reliable4
- Open, powerful, stable3
- Scalable3
- Quick cloud setup3
- Promotes modern/good infrascture practice3
- Backed by Red Hat2
- Cloud Agnostic2
- Runs on azure2
- Custom and extensibility2
- Captain of Container Ship2
- A self healing environment with rich metadata2
- Golang1
- Easy setup1
- Everything of CaaS1
- Sfg1
- Expandable1
- Gke1
Pros of Titus
Sign up to add or upvote prosMake informed product decisions
Cons of Kubernetes
- Poor workflow for development15
- Steep learning curve14
- Orchestrates only infrastructure7
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional Technology Overhead1
- More moving parts to secure1
- Additional vendor lock-in (Docker)1
Cons of Titus
Sign up to add or upvote consMake informed product decisions
What is Kubernetes?
What is Titus?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Titus?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kubernetes?
What tools integrate with Titus?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+1
+2
+9
+11
+11+7
+12
+2