4 ms·
It is a big deal, because I (my last employer) spent ten(s?) of thousands of dollars on VMware so that I would not have to put infrastructure nodes on bare meta
by yebyen 9y ago
It is a big deal, because I (my last employer) spent ten(s?) of thousands of dollars on VMware so that I would not have to put infrastructure nodes on bare metal. They created vSAN so it would be so. (Modern infrastructure I'm sure has better solutions than vSAN, but it worked great for us, and I'm out of there now. We never honestly needed that until we had large Windows servers to take care of. I personally have a distaste and distrust for Windows servers, but when the new owner came he was the boss, and that was where they were invested. (Yeah, let's go with invested...))
Some of those infrastructure nodes were Windows machines, and (most) of them were Linux VMs. I have not used Mesos yet (I am using Kubernetes in dev only, but my org has not drank any of the kool-aid yet), it kind of sounds like I want Mesos (and Marathon?) for the same reasons that I wanted VMware when I had only one Windows server and I literally couldn't live without it when I suddenly had dozens more Windows servers.
(I heard that OpenShift will soon run Windows containers.
I can't imagine it will be long after that before Kubernetes at-large also does.)
I'm not sure I need Mesos, Kubernetes does an awful lot, but it still seems like Kubernetes Admin user could royally fuck things up for me on a multi-tenant system that I admin (I learned the ways from OpenShift), if it's just Kubernetes. But on Mesos, maybe I can get some guarantees that I couldn't without it...
I'm not sure how much anyone has a "need" for Mesos. If I understand exactly what makes it different from Kubernetes, it's one of those things that you just kind of layer on top so that when your suspenders fall right off for some reason, your belt actually can still keep your pants up.
I honestly don't know any more about Mesos than what I've been told, but as a belt-and-suspenders kind of guy I think it could actually be for me. What say you to that?
- haimez 9y agoAhem... Millennials.
- dang 9y agoWould you please not post unsubstantive comments to HN? https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- devonkim 9y agoOne of the problems I've heard with Mesos is that it would require your application code to need to use its constructs - this may not be true or inaccurate now. For a K8s pod, you create a container and it doesn't need to be rewritten unless it's stateful and is not really a 12 factor design application. Mesos' originating use cases come from stateful big data ish systems like Hadoop and Zookeeper clusters, and K8s aimed more at containerized web application infrastructures and both are filling out use cases the other direction nowadays. From a risk perspective, unless something terrible happens with K8s adoption soon in 4 years I expect every other shop to be using K8s in production and many, many more people will know how to run it day to day than they do now. With that said, adoption is quite slow in some places and nothing is assured.