Apache Mesos to be moved to Attic
21–30 of 139 posts
Re: Apache Mesos to be moved to Attic
#22https://www.amd.com/system/files/documents/new-epyc-case-stu...
Re: Apache Mesos to be moved to Attic
#23Never in my life did I meet such an arrogant group of people.
First, they left us waiting in reception for an hour.
They eventually took the meeting over lunch, where we had to watch them inhaling their free food.
Some guy in plastic-leather trousers spent most of the hour lecturing us about all of the multi million deals they were doing, and how they weren't interested in speaking with anyone who couldn't write 7 figure checks.
Not once did they ask about our business or even our names if I remember correctly.
I had a similar experience with other west coast tech companies. Too arrogant for their own good and not able to put in the hard yards with stodgy old enterprise companies even when they have good technology and are early to market.
Re: Apache Mesos to be moved to Attic
#24I went to see Mesos early in their life in their San Francisco office after a joint customer put us in touch. Never in my life did I meet such an arrogant group of people. First, they left us waiting in reception for an hour. They eventually took the meeting over lunch, where we had to watch them inhaling their free food. Some guy in plastic-leather trousers spent most of the hour lecturing us about all of the multi…
Re: Apache Mesos to be moved to Attic
#25Re: Apache Mesos to be moved to Attic
#26Mesos made a ton of new contributions to distributed resource management. Resource offers and application integration can allow high cluster utilization and efficiency. Giving applications the opportunity to take part in resource allocation and scheduling was similar to the Exokernel design, and led to many interesting middleware architectures. Mesos also introduced Dominant Resource Fairness for allocating resources…
Re: Apache Mesos to be moved to Attic
#27This seems to be true both for the Omega experiments at Google (which I assume still uses Borg), and for Mesos. In the end, Mesos always lacked even a minimal application deployment story. Marathon unfortunateley never got beyond being a shiny UI with a primitive application model and a hacky API.
I think if Mesos(-sphere) had recognized that gap in time, and came up with a decent framework for application deployments, instead of telling everyone to write their own framework (in C++, against a hacky code base), Kubernetes might not have had a chance, or at least we would have two alternatives to chose from. Too bad.
Re: Apache Mesos to be moved to Attic
#28I went to see Mesos early in their life in their San Francisco office after a joint customer put us in touch. Never in my life did I meet such an arrogant group of people. First, they left us waiting in reception for an hour. They eventually took the meeting over lunch, where we had to watch them inhaling their free food. Some guy in plastic-leather trousers spent most of the hour lecturing us about all of the multi…
You're thinking of Mesosphere, a separate company building a product on top of Mesos.
I ran one of the first Docker partners and saw first hand how both Mesos and Docker Inc had considerable mindset and interest from large enterprises for a year or so before Kubernetes matured.
They both spectacularly failed to deliver through arrogance and bad execution.
Re: Apache Mesos to be moved to Attic
#29I used Mesos for a few years before experiencing Kubernetes. As neat as Mesos was, it was doomed from the start. For one, Kubernetes was, at least to some extent, a rewrite and extraction of functionality built at Google, from their production orchestration ecosystem that is Borg. The fact that Kubernetes was heavily influenced by a successful, large solution in this space allowed it to leapfrog, at least a bit, the…
Re: Apache Mesos to be moved to Attic
#30End of an era... Are there any viable alternatives to Kubernetes and Nomad?