the promise of a cloud native platform (20160504)

@bridgetkromhout

The Promise of a Cloud Native Platform

Bridget Kromhout

@bridgetkromhout

lives: Minneapolis,

Minnesota

works: Pivotal

podcasts: Arrested DevOps

organizes: devopsdays

Bridget Kromhout

@bridgetkromhout Image credit: Holly Bailey/Yahoo News

@bridgetkromhout

Traded oncall… …for more travel (Similar effect on sleep)

@bridgetkromhout

quoted in “10+ Deploys Per Day: Dev and Ops Cooperation at Flickr” at Velocity 2009

John Allspaw & Paul Hammond

“In the last week there were 67 deploys of 496 changes by 18 people”

Flickr Dev Blog, December 17th 2008

Image credit: visual_dichotomy on Flickr

@bridgetkromhout

Failure: what does recovery look like?

Environments: how long to spin up a new one or copy an existing one?

Deploys: how often? how long do they take? How often do they go wrong?

Why don’t we all move that fast today?

@bridgetkromhout

Not the goal: “automate all the things”

@bridgetkromhout

The goal: shorter time from idea to value

Image credit: leadliasionImage credit: thebigword

@bridgetkromhout

How do we get to

the goal?

@bridgetkromhout

The Wall of Confusion

yolo nope

@bridgetkromhout

navigating choices

@bridgetkromhout

@bridgetkromhout

devops is practiced,

not purchased.

Image credit: scriptrock

@bridgetkromhout

Land of 10,000 devops clichés

@bridgetkromhout

Image credit: xkcd

@bridgetkromhout

Docker in Production: Reality, Not Hype

@bridgetkromhout

Deconstructing a Python/Django monolith into Dockerized Go microservices (as was the style at the time)

How to win at buzzword bingo:

@bridgetkromhout

Image credit: James Ernest

@bridgetkromhout

Two-Pizza teams

@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

@bridgetkromhout

CA

CP AP

AvailabilityConsistency

Partition Tolerance

“a partition is a time bound

on communication.”Eric Brewer

@bridgetkromhout

Image credit: Vasa Museet

@bridgetkromhout

@bridgetkromhout

so what’s a cloud native platform?

@bridgetkromhout

Image credit: Simon Wardley

@bridgetkromhout

opinions optional

if you can deploy and operate code in any capacity, you

have a platform

@bridgetkromhout

@bridgetkromhout

reasonable constraints

@bridgetkromhout

Minimum Viable Platform

1. Routing and load balancing 2. Backing services broker 3. Infrastructure orchestration 4. Health management, monitoring, and recovery 5. Immutable artifact repository 6. Log aggregation

Casey West - The cloud-native future

@bridgetkromhout

structured contracts determine the promises a platform can keep

@bridgetkromhout

Large-scale cluster management at Google with Borg - Verma et al. 2015

“Almost every task run under Borg contains a built-in HTTP server that publishes information about the health of the task and thousands of performance metrics”

@bridgetkromhout

“Nothing’s the same anymore.”

Babylon 5

Jeffrey Sinclair

Image credit: Astroengine

@bridgetkromhout

Legacy: your

customers & money

live here

@bridgetkromhout

Visvesvaraya Museum, Bengaluru

IBM 1401 (in use until 1989)

@bridgetkromhout

Process: scar tissue from past

failure

@bridgetkromhout

“It’s not necessary to change.

Survival is not mandatory.”

—W. Edwards Deming

@bridgetkromhout

The Wall of Confusion (here there be White Walkers)

@bridgetkromhout

@bridgetkromhout

the right thing should be

the easy thing

@bridgetkromhout

Inaction is still a choice

@bridgetkromhout

12-factor apps need

12-factor ops

@bridgetkromhout

12-factor kitten

@bridgetkromhout

simple patterns automated by

tooling: the cloud native

advantage

Cloud Native Infrastructure Automation

@bridgetkromhout

Cloud Native Application Framework

CPI

BOSH release

12 Factor

Cloud Native Contracts

Cloud Native Runtime Platform

@bridgetkromhout

Thank you!