3 ms·
Mesos was always simpler to deploy and wrap my head around, but Kubernetes obviously won the most mindshare. DC/OS was Mesosphere's "enterprise" offering - howe
by nemothekid 6y ago
Mesos was always simpler to deploy and wrap my head around, but Kubernetes obviously won the most mindshare. DC/OS was Mesosphere's "enterprise" offering - however I wonder what this means for the Mesos product. I know there are still a couple large organizations still using it, but D2iQ employs most of the engineers working on Mesos, which isn't a good sign if they are no longer making money from it.
- wmf 6y agoPretty soon either D2IQ won't employ those engineers or they won't be working on Mesos.
- keymone 6y agoI’ve got the exact opposite experience. Mesos is far more complex to run due to difficulty of developing a framework correctly. Kubernetes made the trade off to schedule centrally and that is probably the correct thing to do and definitely the more easy model to wrap your head around.
- closeparen 6y agoI would venture that most people using Mesos in Kubernetes-like use cases were deploying either DC/OS or Aurora, not writing their own frameworks.
- justincormack 6y agoAll the large Mesos users I know of are moving to Kubernetes, I don’t know which ones you are thinking of.
- dharmab 6y agoDid Apple switch from Mesos? I know with the number of systems they were running Siri on Kubernetes might not have been possible. Then again they have the resources to build an in house replacement.
- cpuguy83 6y agoThey certainly hired a bunch of K8s talent (and still are, I think).
- schmichael 6y agoApple is huge. You will find more than one of every scheduler inside. No clue what their plans are around Mesos, but I think it’s safe to assume there are places it works well and will be slow to change.
- base698 6y agoMesos didn't have a cronjob runner out of the box. There were other features like service discovery that were more intuitive in K8s as well.