[lowbloodsugar]

I have an irrational soft spot for Apache Mesos. I loved the separation of the resource management from the scheduling. Note to self: do not rabbit hole on this. Hm. Maybe mesos is the manager for my agent sandboxes. No! Bad lowbloodsugar!

[hosh]

How are resource management distinct from scheduling in Mesos?

[lowbloodsugar]

Mesos handles resource reservation like a broker. Frameworks like Marathon or applications like Apache Spark make requests to Mesos for resources and then ask Nesos to launch specific processes on those resources. You can have multiple frameworks on a given Mesos cluster.

[hosh]

Is it fair to say that Mesos is more top-down while Kubernetes is more bottom-up in scheduling approach?