I would argue that computer scientists (academia) is the biggest offenders when it comes to writing "non-clean" code. They normally don't have any incentive to create reusable and maintainable code.

I've started working on something along those lines: http://gilliam.github.io/ . Currently using LXC, but adapting to docker is quite easy since "VMs" are provisioned and launched via shell scripts.

I'm skeptical that your bespoke approach is better than gluing together well-known and battle-tested tools, but if you stick at it, you naturally have the chance to do something better, because of the singular vision. Best of luck with this!!

You might be right. I'm betting on the fact that if you compose your system of small decoupled components you can change your mind at a later time. Lets see what happens :)

Usling the monkey, have you found that some design patterns are better than others? For example, queues vs RPC?

My notes, with typos:

http://jrydberg.me/post/18620457405/crash-burn-2012-the-ops-...

Cool. While this deck wasn't too bad, sometimes the video-only presentations without a link to the actual slides really do need notes like this.

Some sane design lessions in the original material: http://www.aosabook.org/en/bdb.html

Why didn't they just use Zookeeper?

There's some discussion of this in the notes from their release announcement: http://xph.us/2011/04/13/introducing-doozer.html

is it just me that thinks dialog boxes sucks?

i don't want to get interrupted in my flow.

design so that you don't need something to pop up in the users face.

I wonder what will happen to Microsoft Smooth Streaming if this happens.

what timezone picker is that?