3 ms·
Thank you for the reply, I appreciate it. But from everything i've read (all the documentation for these frameworks suck, though Mason's is the most readable) s
by peterwwillis 13y ago
Thank you for the reply, I appreciate it. But from everything i've read (all the documentation for these frameworks suck, though Mason's is the most readable) still seems like Mesos supports the features of the previous two tools, for the most part. Is there some reason its feature set wasn't just tweaked a bit to handle those two cases? Like, why is there a distinction between a long-running and a short-running job? Repeating a job is also not an especially complicated task that should require a whole new framework to accomplish.
The reason i'm asking these questions is I want to know if I need to use these tools. It seems like kids these days just immediately grab up every new tool they can and try to shove them into their environment, vs trying to find the right fit or configure them properly. It feels like Marathon and Chronos are mostly unnecessary - this is evident once you realize Mesos is a framework you can build on to do the same things Marathon and Chronos do with a lot less complexity.
- florianleibert 13y agoIf you have specific requests on how to make the docs for these frameworks better, it'd be great if you filed a ticket on their respective github page.