* Overview: https://netflix.github.io/titus/overview/ * Prerequisites: https://netflix.github.io/titus/install/prereqs/ * Building Code: https://github.com/Netflix/titus-executor/blob/master/README... * ACM Queue Article: https://queue.acm.org/detail.cfm?id=3158370 * License: APL 2.0
* Overview: https://netflix.github.io/titus/overview/
* Prerequisites: https://netflix.github.io/titus/install/prereqs/
* Building Code: https://github.com/Netflix/titus-executor/blob/master/README...
* ACM Queue Article: https://queue.acm.org/detail.cfm?id=3158370
* License: APL 2.0
Any high level reasons Titus will win on AWS long term?
As awesome as kubernetes is and is becoming, I've always been a fan of the Mesos architecture. For managing large, complex, diverse workloads, it's perfect.
At this point they have surely recognized that internal closed tools will never compete with the velocity allowed by a huge open source project like Kubernetes and they are left with two options:
* Recognize the sunk cost of Titus, avoid the relevant fallacy, and migrate to Kubernetes
* Make Titus open source and hope that enough community can be built around it to justify the long-term cost of continuing its use internally.
It certainly is possible Titus gains a lot of steam, particularly from orgs that are already on Mesos, and be a viable long-term option. However, if I was a betting man, I'd say that 10 years from now the world has moved on and even Netflix will be using Kubernetes, or the future iteration of container-orchestration orchestrator that will inevitably be built on top of it.
