10 engineers on Hacker News describe using Marathon first-hand: 3 endorse it, 2 regret it, 0 are mixed.
“We were happy with our Mesos/Marathon cluster of ~100-200 machines”
endorse · production · CoffeeDregs · 2017-09-06 · source ↗ · wrong label?“I've run a number of clusters in production now for just over a year with Marathon and it pretty much "just works."”
endorse · production · 1 yr · bogomipz · 2016-12-25 · source ↗ · wrong label?“I have been running Marathon in production to power more than 100 applications for the past six months... I am actively moving away from Marathon because of these issues.”
regret · production · 0.5 yr · steve0ps · 2015-06-12 · source ↗ · wrong label?“My (completely casual) experience with Marathon is pretty bad, with the main process crashing quite regularly even under no load”
regret · personal · Wilya · 2015-06-12 · source ↗ · wrong label?“We now use mesos+marathon(+chronos for deployment) for running our docker container, which sounds much more overkill than chef, but turned out to work much better and cleaner.”
endorse · production · hobofan · 2014-11-19 · source ↗ · wrong label?“In my org, we run open source Marathon/Mesos deployments for years without any DC/OS additionals”
neutral · production · perfect_kiss · 2019-11-17 · source ↗ · wrong label?“In practice we run all of our Mesos tasks and Marathon services in containers anyway, as you mentioned.”
neutral · production · dharmab · 2018-09-27 · source ↗ · wrong label?“we run a HA Neo4j DB deployment as a Marathon service pegged to a handful of nodes”
neutral · production · estill01 · 2017-09-06 · source ↗ · wrong label?“Orchestrations through mesos and marathon.”
neutral · production · avitzurel · 2016-11-21 · source ↗ · wrong label?“we can continue to deploy Docker through Mesosphere Marathon onto Mesos as we've been doing.”
neutral · production · potto · 2014-12-04 · source ↗ · wrong label?