Ops in the time of serverless containerized webscale (AATC)

@bridgetkromhout
Ops in the time of
serverless containerized webscale

@bridgetkromhout
lives:
Minneapolis,
Minnesota
works:
Pivotal
podcasts:
Arrested
DevOps
organizes:
devopsdays
Bridget Kromhout

@bridgetkromhout
traded oncall… …for more travel (similar eﬀect on sleep)

@bridgetkromhout
serverless
(in the brave new cloudy-with-a-chance-of-containers world)

@bridgetkromhout
— Simon Wardley

@bridgetkromhout
“Nothing’s the same anymore.”
Jeﬀrey Sinclair
Babylon 5

@bridgetkromhout
containers:
dawn of the third age?

@bridgetkromhout
1979 (Version 7) 
1982 (BSD)
20042000
chroot FreeBSD jails Solaris Zones LXC
2008
A Brief History of Containers, Part 1
(before docker era)

@bridgetkromhout
A Brief History of Containers, Part 2
(docker common era)
2011
Cloud Foundry
2013
Docker
2014
Rocket (later rkt)
2015
Open Container
Initiative

@bridgetkromhout
architectural considerations

@bridgetkromhout
container tradeoﬀsContainers limit attack
surface & emitters don’t
need ports open
but…
Microservices move IPC
to network transactions &
complexity is distributed

@bridgetkromhout
xkcd.com/208/

@bridgetkromhout
“cattle,
not pets”
(even
adorable
Attack
Kittens)

@bridgetkromhout
Image credit: xkcd

@bridgetkromhout
monitoring: the old way

@bridgetkromhout
The business:
UX data for product &
engineering
Measure value delivered
Information Technology:
Visibility into state and failures
Product & engineering decisions
Measure success of projects
monitoring needs of…
The Art of Monitoring (2016)
James Turnbull
artofmonitoring.com

@bridgetkromhout
monitoring: the new way

@bridgetkromhout
Image credit: James Ernest

@bridgetkromhout Image credit: Wikipedia
“Any organization that designs a system…
will produce a design
whose structure is a copy of
the organization's
communication
structure.”
Mel Conway

@bridgetkromhout Image credit: 00abstrahiert99 on Flickr
…but #opslife
means I’m a
cynical realist

@bridgetkromhout
just say no to “awesome mode” vs “sad mode”
Image credit: stock
bimodal IT?!?

@bridgetkromhout
The Wall of Confusion

@bridgetkromhout
The Wall of Confusion
yolo nope

@bridgetkromhout
cautionary tales

@bridgetkromhout
tree failure?!?

@bridgetkromhout
be explicit: what’s obvious to you isn’t a universal to all

@bridgetkromhout
a tranquil beach… or is it?

@bridgetkromhout
be adaptable: try a diﬀerent approach

@bridgetkromhout
a solitary warning

@bridgetkromhout
let’s take a closer look…

@bridgetkromhout
warn early & often

@bridgetkromhout
things fall apart

@bridgetkromhout
Who owns your availability? The answer may surprise you!
Image credit: Wikipedia

@bridgetkromhout
observability: answering questions we didn’t know to ask

@bridgetkromhout
communication &
disconnects

@bridgetkromhout
"The past is never dead. It's not even past.”
William Faulkner

@bridgetkromhout
not actually
20 units of devops

@bridgetkromhout
silos are for grain

@bridgetkromhout
still computers

@bridgetkromhout
Computers are easy;
people are hard

@bridgetkromhout
Massively scalable fault-tolerant
distributed systems require a
signiﬁcant engineering eﬀort to build
and operate; complex socio-technical
systems are even more challenging.
Computers are easy;
people are hard

@bridgetkromhout
the journey:
automation
provisioning
monitoring
architecture
culture

@bridgetkromhout
We are uncovering better ways of developing
software, by doing it and helping others do it

Ops in the time of serverless containerized webscale (AATC)

More Related Content

What's hot

Similar to Ops in the time of serverless containerized webscale (AATC)

More from bridgetkromhout

Recently uploaded

Ops in the time of serverless containerized webscale (AATC)