5 ms·

Titus, the Netflix container management platform, is now open source

• yarapavan 8y ago
  Resources: * Overview: https://netflix.github.io/titus/overview/ https://netflix.github.io/titus/overview/ * Prerequisites: https://netflix.github.io/titus/install/prereqs/ https://netflix.github.io/titus/install/prereqs/ * Building Code: https://github.com/Netflix/titus-executor/blob/master/README.md#building https://github.com/Netflix/titus-executor/blob/master/README... * ACM Queue Article: https://queue.acm.org/detail.cfm?id=3158370 https://queue.acm.org/detail.cfm?id=3158370 * License: APL 2.0
  • nacs 8y ago
    With linebreaks: * Overview: https://netflix.github.io/titus/overview/ https://netflix.github.io/titus/overview/ * Prerequisites: https://netflix.github.io/titus/install/prereqs/ https://netflix.github.io/titus/install/prereqs/ * Building Code: https://github.com/Netflix/titus-executor/blob/master/README.md#building https://github.com/Netflix/titus-executor/blob/master/README... * ACM Queue Article: https://queue.acm.org/detail.cfm?id=3158370 https://queue.acm.org/detail.cfm?id=3158370 * License: APL 2.0
• kenhwang 8y ago
  Maybe the announcement was a bit too early? I don't actually see source code anywhere.
  • despacito 8y ago
    the source code is linked at the bottom of the README in https://github.com/Netflix/titus https://github.com/Netflix/titus
    • kenhwang 8y ago
      Ah, thank you.
  • jalk 8y ago
    Or perhaps a little too late!
    • kenhwang 8y ago
      Can't wait for the great KuberMesosTitus merge together monstrosity!
      • eliaspro 8y ago
        ...a multi-vendor multi-implementation OpenContainerStack. What could go wrong?
• jaaron 8y ago
  So happy to see this. 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.
  • deleted 8y ago
    [deleted]
• moondev 8y ago
  Very excited to try this out finally. Integration with netflix OSS ecosystem seems like it will be a big win for moving those dependant services off ec2
• robbyt 8y ago
  Other than the deep integration with AWS, can anyone help me understand what's different with this compared to the other various container schedulers?
  • CSDude 8y ago
    It also considers bandwidth requirements as I see, which Netflix surely needs and schedules containers accoridng to that, because of each network interface and instance has some limits.
• ec109685 8y ago
  Are there long term architectural advantages that Titus will have over Kubernetes? Given K8s is multi cloud it seems like the investment there will continue to be very strong and will eclipse Titus, even on AWS. Any high level reasons Titus will win on AWS long term?
• coryfklein 8y ago
  Titus seems to be the cost of Netflix's brilliant engineering talent. They clearly had a need for container orchestration before Kubernetes was available and by this point they have sunk years of effort into their current investment in Titus. 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.