San Francisco, California
2015-11-16 to 2015-11-18
Speaker
Bridget Kromhout
Description
What is your platform? Everyone has one, whether it's Docker wrapped in config management wrapped in thousand-line fabfiles, bespoke artisanal hand-crafted shell scripts… or both! What promises can your platform make and keep? What contract does your platform provide to your applications? Does your platform deliver value rapidly, reliably, at scale... or has it become a burden unto itself? Perhaps a bit of both?
Continuous delivery has gone from an aspirational nice-to-have to a must-have capability for staying competitive at the edge of innovation. Nearly every automation project sets out to provide self-service deployments for developers with visibility and reliability for operations. Whether using configuration management or embracing containers to package workloads, we need a long list of capabilities to fill gaps in the automation. How do you provision infrastructure? Who can provision? How much? How do you deploy? Who can do deployments? What can even get deployed? What about canary deploys? Rolling deployments? Monitoring? Metrics? Fault detection? Fault remediation? Everyone across the industry has needed to handcraft a platform specific to their organization. (I've done it. I bet you have too.)
The operational needs of a continuously delivered microservice architecture bring with them new considerations and constraints. If the cost of deploying and operating a service is high, in terms of time or resources, deploying more things more frequently sounds like a really bad idea. The era of ad-hoc automation is coming to an end as the patterns of cloud native organizations who move quickly and safely are becoming more apparent. Between rolling your own from open-source components and implementing a turn-key platform solution, a vast array of choices exists. I'll talk about where I've been (spoiler alert: containers in production without hype) and what I've learned on this journey.
Video of this session available at InfoQ site
"Did you just yolo that into production?!" - @bridgetkromhout at #qconsf
— Bryan Cantrill (@bcantrill) November 17, 2015
“If you are building something local to your organization then your expertise becomes local to your organization” @bridgetkromhout #qconsf— Ines Sombra (@randommood) November 17, 2015
@bridgetkromhout drops knowledge like its hot #qconsf pic.twitter.com/8VOe3lSy8N — Ines Sombra (@randommood) November 17, 2015
Sometimes you need to think value-add and choose 'boring software' over going the bespoke infrastructure route. #qconsf @bridgetkromhout
— Jeremy Williams (@jbillybytes) November 17, 2015
"Just because you can build things it doesn't mean you should" the wisdom of @bridgetkromhout #QConSF pic.twitter.com/w6FVR71jNt — Ines Sombra (@randommood) November 17, 2015
because you can doesn't mean you should. excellent point. @bridgetkromhout #qconsf
— Jeremy Williams (@jbillybytes) November 17, 2015
So true!! Periodic reminder that shitty lives forever from @littleidea & @bridgetkromhout #QConSF pic.twitter.com/5sM0SrRyb9 — Ines Sombra (@randommood) November 17, 2015
"Containers aren't going to fix your broken culture!" - @bridgetkromhout breaking the tough news at #qconsf
— Bryan Cantrill (@bcantrill) November 17, 2015
Cool to see @bridgetkromhout channeling @swardley at @QConSF #PaaS pic.twitter.com/pXzudGyb90
— adrian cockcroft (@adrianco) November 17, 2015
Ridiculously excellent talk by @bridgetkromhout @QConSF really hoping the video will be out soon #mustwatch — Ines Sombra (@randommood) November 17, 2015
.@bridgetkromhout asks if your platform can offer these things... #qconsf pic.twitter.com/PqmW5u39Yg
— Jon Moore (@jon_moore) November 17, 2015
@starbuxman SHE HAS MY VOTE!! 😍 such an amazing talk @bridgetkromhout @caseywest — Ines Sombra (@randommood) November 17, 2015
.@bridgetkromhout : "Make the right thing be the easy thing" #qconsf < systems thinking!
— Jon Moore (@jon_moore) November 17, 2015
You shouldn't let devs "YOLO that into production" but give them the tools to reduce the downside of taking risks @bridgetkromhout #qconsf
— Siamak Khoubyari (@khoubyari) November 18, 2015
Truth RT @randommood: “Just because you can build things it doesn’t mean you should” the wisdom of @bridgetkromhout https://t.co/vUrVrf6vpB
— Don Browning (@donwb) November 18, 2015
.@bridgetkromhout provides advice on navigating #devops Tooling and Platforms pic.twitter.com/vkF0CDXvaV
— QCon San Francisco (@QConSF) November 18, 2015
Lessons learned by @bridgetkromhout on challenges of ad hoc automation, constraints, micro-services #structureconfhttps://t.co/oF3lXYo6lE
— Tom Killalea (@tomk_) November 18, 2015
The fantastic @bridgetkromhout Beyond Ad-hoc Automation: To Structured Platforms https://t.co/QbM1wxn9yl
— Adib Saikali (@asaikali) January 4, 2016
'Beyond Ad-hoc Automation: To Structured Platforms' @bridgetkromhout presentation from the #qconsf containers track https://t.co/whKqtNbRjb
— Chris Swan (@cpswan) January 4, 2016
Beyond Ad-hoc Automation: To Structured Platforms https://t.co/GnEJfSL5Tb < fun presentation by @bridgetkromhout
— Richard Seroter (@rseroter) January 4, 2016