Hacker News Reader

Comment by 23david | Hacker News Reader

Yep. In my experience, I've seen that the issue isn't with Mesos the Apache project, but rather with Marathon and Chronos, which are the applications built by Mesosphere.

There's a big naming and marketing confusion at the moment with the open-source project and the VC-funded startup having such a similar name. It's unfortunately giving a bad reputation to the Mesos project.

Curious why there actually isn't a trademark issue here...?

View on HN

Because Mesosphere (the VC backed startup) hired the creator of Mesos (the Apache project), and is now trying to capitalize on the open source project as one of their "products".

Mesosphere is arguably the largest contributor to Mesos, certainly on par with Twitter, especially when you consider all the surrounding ecosystem. The company also secured permission from the Apache foundation with the trademark when the company was founded. It's good for the open source ecosystem to have companies productize and support projects, particularly when they are plowing millions of dollars back into the open source.

FWIW, I've had much more success with HubSpot's Singularity than Marathon/Chronos. (I use Marathon to bootstrap Singularity as the "init system", because it had HA before Singularity, but that's the extent of its interaction with my system.)

That's interesting. I've also found it interesting that one of the big selling points of the Mesosphere ecosystem is that it is used at scale by Twitter. But AFAIK twitter developed their own framework for long running tasks (http://aurora.incubator.apache.org/). So they are using Mesos (the open source project), maybe Chronos, and their own version of Marathon. That can be somewhat misleading to newcomers.

To be clear, Twitter runs Aurora which is open source and has proven itself to be stable, battle-tested, and scalable; development on Aurora began in 2010, and over the years Mesos and Aurora have evolved together. Aurora has cron capabilities built into it, and Twitter does not run Marathon or Chronos.

Twitter engineering recently blogged about Aurora with a bit more on its history: https://blog.twitter.com/2015/all-about-apache-aurora, and The New Stack recently published a two-part article on the project: http://thenewstack.io/twitters-aurora-relates-googles-borg-p..., http://thenewstack.io/twitters-aurora-replaces-operating-sys...

(full disclosure, I work at the tweet shop)

Marathon is used in production at our company on > 1,000 servers. 0.7.x had some stability problems but 0.8 has been terrific. Especially given the project seems to be less than 2 years old (according to github), I find it to be really stable. A lot of advanced canary-style deploy features were added and they're more advanced and scalable than anything else we tried out.

Reply on news.ycombinator.com