Boston, Massachusetts
2017-04-19 to 2017-04-21
Description
So you’ve deployed your app, launched your site, and gone live in prod: so far, so good. But what happens when people actually use it, when you find out where your IaaS rate-limits you, and when you can’t just throw (virtual) hardware at your software problems?
Let’s explore the practical realities in that vast, uncharted space between “waiting for the change control board is probably fine” and “we just implemented a novel time series data store in our spare time.” If you’re coming to this talk, you may be well past the former, while the latter remains strictly aspirational. What matters these days in operations when you’re dockering all the Dockers, going serverless with lambda functions, or scaling beyond what you’ve seen before? Getting the abstractions right is a non-trivial task.
I’ll chat about the new stuff worth running in production, dispel myths (NoOps is not a thing; serverless still has servers), and answer questions (spoiler alert: the answer is “it depends”). If you’ve put in a non-zero number of hours on the pager and still can joke about it, you know that a Someone Else’s Problem field lasts just long enough for it to become our problem. Let’s talk solutions.
Slides
Video - (reg-wall)
Tweets
Kicking off with @bridgetkromhout bringing the devops perspective into #AATC2017 <3 'cloudy with a chance of containers'
— Laura Bell (@lady_nerd) April 19, 2017
"Guess what, there are servers with #serverless! You are just choosing your abstraction level, and that's cool" @bridgetkromhout #AATC2017 pic.twitter.com/OV6pAi20b7
— Daniel Bryant (@danielbryantuk) April 19, 2017
My new fav phrase: "Verbing weirds language" @bridgetkromhout #AATC2017
— Elisabeth Hendrickson (@testobsessed) April 19, 2017
— Bridget Kromhout (@bridgetkromhout) April 19, 2017
Where @bridgetkromhout explains that "serverless" is more about choosing the level of abstraction that you're focused on. #AATC2017 pic.twitter.com/g5f3oSpebf
— Richard Seroter (@rseroter) April 19, 2017
The progression of containers isn't about new tech, it's about making them more usable and accessible. @bridgetkromhout @pivotal #AATC2017 pic.twitter.com/XD1FDQ5PNI
— Laura Bell (@lady_nerd) April 19, 2017
The history of Linux containers from @bridgetkromhout at #AATC2017 pic.twitter.com/BFlXZ1MoYT
— Daniel Bryant (@danielbryantuk) April 19, 2017
"Containers are cool, but ask what you want to achieve. You are delivering business value, not just cool tech" @bridgetkromhout #AATC2017 pic.twitter.com/EZ2O6ZeQlP
— Daniel Bryant (@danielbryantuk) April 19, 2017
Containers can give small attack surface if you strip down the software stack but trade offs happen @bridgetkromhout #AATC2017 #Security
— Laura Bell (@lady_nerd) April 19, 2017
More talks need adorable attack kittens @bridgetkromhout 💗💗💗💗 pic.twitter.com/PIhNy3BPdX
— Laura Bell (@lady_nerd) April 19, 2017
Cloud is a forcing function for finding out what's slow in your organization. - @bridgetkromhout #AATC2017
— Richard Seroter (@rseroter) April 19, 2017
Nice shout to @kartar's "Art of Monitoring" book by @bridgetkromhout at #AATC2017. Monitor biz outcomes over (in addition to) tech issues pic.twitter.com/72jLgHd8w6
— Daniel Bryant (@danielbryantuk) April 19, 2017
Love that @bridgetkromhout managed to get a reference to the Settlers of Catan into her talk. #AATC2017
— Elisabeth Hendrickson (@testobsessed) April 19, 2017
Love the law of "Conservation of Complexity" - @bridgetkromhout credited someone else for the phrase (who?) #AATC2017
— Elisabeth Hendrickson (@testobsessed) April 19, 2017
I was quoting @0x74696d about conservation of complexity when one moves to a microservices architecture. #aatc2017
— Bridget Kromhout (@bridgetkromhout) April 19, 2017
"One of the problems with microservices is murder-mystery-troubleshooting. Cross-team collaboration is key." -- @bridgetkromhout #AATC2017
— Elisabeth Hendrickson (@testobsessed) April 19, 2017
"Having good tooling is necessary but is not sufficient." -- @bridgetkromhout #AATC2017
— Elisabeth Hendrickson (@testobsessed) April 19, 2017
"Just say no to bi-modal IT..." :-) @bridgetkromhout #AATC2017 pic.twitter.com/gz1J1QPmnO
— Daniel Bryant (@danielbryantuk) April 19, 2017
Change will always be a factor. We have to roll with it. Life aim for maximum chaos. @bridgetkromhout #AATC2017
— Laura Bell (@lady_nerd) April 19, 2017
Sage advice from @bridgetkromhout at #AATC2017 on building software "The people stuff is even more challenging" pic.twitter.com/B3uHg28d3n
— Daniel Bryant (@danielbryantuk) April 19, 2017