I got the chance to play with Joyent's Triton Elastic Container Service. Yes, the trade-off between resource isolation and efficient usage would disappear since

I got the chance to play with Joyent's Triton Elastic Container Service. Yes, the trade-off between resource isolation and efficient usage would disappear since they use SmartOS zones rather than Linux namespaces or cgroups to provide strong isolation between containers. They have forked Mesos[1] and added capability to run Triton containers as Mesos tasks[2]. Some of the questions which need to be explored: - Whether they provide some kind of built-in service discovery. - Whether all existing Mesos frameworks will support Triton based Mesos deployment since many frameworks make use of different networking modes, docker storage engine. [1]: https://github.com/joyent/mesos https://github.com/joyent/mesos [2]: https://www.joyent.com/blog/mesos-by-the-pound https://www.joyent.com/blog/mesos-by-the-pound