3/10 patronizing and FUD. Mesos is happy to limit resources with cgroups etc. When you say every process can modify the state shared by every other process

3/10 patronizing and FUD. Mesos is happy to limit resources with cgroups etc. When you say every process can modify the state shared by every other process in italics (the scariest type variant), do you mean ‘the filesystem’? Mesos has a swathe of isolators to choose from to enforce separation. Mesos is also happy to let tasks run as a specific user, so the good old Unix process model will stop random tasks from stomping each other. Did you see the other comments drawing attention to the inequality of the Mesos/Kubernetes comparison & suggesting Marathon as the more appropriate peer technology?