Oh, we're full of beans. And teaching client developers how we work is literally what Pivotal Labs aims to do. It's probably the first place I've worked that has a high rate of reverse-churn: people leaving to work at startups for the glamour or equity, then deciding they miss Labs and coming back.
As for Diego, start with Onsi Fakhouri's keynote at the Cloud Foundry Summit this year[1], then read Amit Gupta's blog post on app placement as an optimisation problem[2], then you might like the Diego Design Notes repo[3].
My main pet peeve with Diego is the confusing, punny names, so it will be confusing at first.
I'm not familiar with Marathon, but I will read up on it. Thanks.
I find it interesting how everyone is sprinting toward PaaSes from their own positions. For example, Docker is racing up the stack, Hashicorp and Mesosphere are growing sideways, Cloud Foundry is growing in about 5 directions at once. Red Hat is trying to reboot OpenShift with Docker and Kubernetes, but I am not sure how well that will turn out for them.
There's also a thriving cottage industry of people reinventing central controllers that won't scale in the face of the network fallacies, something that Mesos and Diego have accepted and moved on from.
As for Diego, start with Onsi Fakhouri's keynote at the Cloud Foundry Summit this year[1], then read Amit Gupta's blog post on app placement as an optimisation problem[2], then you might like the Diego Design Notes repo[3].
My main pet peeve with Diego is the confusing, punny names, so it will be confusing at first.
[1] https://www.youtube.com/watch?v=1OkmVTFhfLY
[2] http://blog.pivotal.io/cloud-foundry-pivotal/products/app-pl...
[3] https://github.com/cloudfoundry-incubator/diego-design-notes