I am mostly curious about the Mesos layer itself.
Mesos is dead. So you need in-house expertise to patch it without being able to leverage community knowledge.
Does Twitter retain enough people to manage Mesos?
Mesos is dead. So you need in-house expertise to patch it without being able to leverage community knowledge.
Does Twitter retain enough people to manage Mesos?
Also, the article seems to suggest Twitter only has two datacenters. That seems surprising for the global reach of the company. Perhaps there are other smaller datacenters that are not prepared to handle the entirety of the site’s traffic.
My current thinking is there’s time to figure out how to operate the current system before it runs into issues that would render it degraded for a prolonged period of time. I noticed TLS certs have already rotated for instance. That was my best guess for simple thing that could fail if managed poorly.
Apple is also a big Mesos user, but also moving to k8s.
Then Mesosphere (a company) wanted to bring it to the enterprise market but at the time was competing with Kubernetes... and we all know who won.
> Mesos began as a research project in the UC Berkeley RAD Lab by then PhD students Benjamin Hindman, Andy Konwinski, and Matei Zaharia, as well as professor Ion Stoica.
> The social networking site Twitter began using Mesos and Apache Aurora in 2010, after Hindman gave a presentation to a group of Twitter engineers.