News for hackers. Stuff that matters.
Re:Why Always Docker? by jacques_chester on Sunday January 17, 2016 @05:49PM (#10921469)
Put another way: Google has built several generations of internal PaaSes.

This unblocks continuous deployment at the final step, so latency from idea to production falls from years/months/weeks to hours. Or minutes.

Docker's had an interesting life: they built a PaaS, discarded the PaaS, now they're building a PaaS. Because that's what most developers actually need for their daily lives.

It turns out that tinkering with V8s is a lot of fun for a lot of people, but most drivers just want to know how to turn on the car and have the same basic interface work for any workload: wheel, accelerator, brake.

Disclaimer: I work for Pivotal, which is the majority donor of engineering effort to Cloud Foundry, a PaaS inspired in part by Google's experiences.

Re:Why Always Docker? by melted on Sunday January 17, 2016 @06:03PM (#10921525)
I wouldn't quite go as far as to call Borg a PaaS. It's at a somewhat lower level, closer to IaaS. You get a known quantity from it in the form of a stable, tuned, stripped down underlying Linux image, plus a relatively small set of services, but you can deploy pretty much whatever the hell you want without a lot of constraints a "true" PaaS would force you to accept.
Re:Why Always Docker? by jacques_chester on Sunday January 17, 2016 @07:18PM (#10921784)
My understanding is that BOSH is the closest to this from the Cloud Foundry ecosystem.
Re:Why Always Docker? by michaelbuckbee on Monday January 18, 2016 @12:35AM (#10922706)
This mirrors my understanding: that Docker is awesome if you want to build your own PAAS. Otherwise use CF, Heroku or whatever.