The Promise of a Cloud Native Platform (20160712)

54
@bridgetkromhout The Promise of a Cloud Native Platform Bridget Kromhout

Transcript of The Promise of a Cloud Native Platform (20160712)

Page 1: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

The Promise of a Cloud Native Platform

Bridget Kromhout

Page 2: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

lives: Minneapolis,

Minnesota

works: Pivotal

podcasts: Arrested DevOps

organizes: devopsdays

Bridget Kromhout

Page 3: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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

Page 4: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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

Image credit: visual_dichotomy on Flickr

Page 5: The Promise of a Cloud Native Platform (20160712)

@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

Page 6: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Why don’t we all move that fast today?

Page 7: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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

Why don’t we all move that fast today?

Page 8: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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?

Page 9: The Promise of a Cloud Native Platform (20160712)

@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?

Page 10: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Not the goal: “automate all the things”

Page 11: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

The goal: shorter time from idea to value

Image credit: leadliasionImage credit: thebigword

Page 12: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

How do we get to

the goal?

Page 13: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

How do we get to

the goal?

Page 14: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

The Wall of Confusion

Page 15: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

The Wall of Confusion

yolo nope

Page 16: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

navigating choices

Page 17: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 18: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

devops is practiced,

not purchased.

Image credit: scriptrock

Page 19: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Land of 10,000 devops clichés

Page 20: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Image credit: xkcd

Page 21: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Docker in Production: Reality, Not Hype

Page 22: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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

How to win at buzzword bingo:

Page 23: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 24: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Image credit: James Ernest

Page 25: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Two-Pizza teams

Page 26: The Promise of a Cloud Native Platform (20160712)

@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

Page 27: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

“Effective devops tools enable automation

without isolating humans from the automation

process”

Jennifer Davis

Page 28: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 29: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

CA

CP AP

AvailabilityConsistency

Partition Tolerance

“a partition is a time bound

on communication.”Eric Brewer

Page 30: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Image credit: Vasa Museet

Page 31: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 32: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

so what’s a cloud native platform?

Page 33: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Image credit: Simon Wardley

Page 34: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

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

have a platform

Page 35: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

opinions optional

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

have a platform

Page 36: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 37: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

reasonable constraints

Page 38: The Promise of a Cloud Native Platform (20160712)

@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

Page 39: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

structured contracts determine the promises a platform can keep

Page 40: The Promise of a Cloud Native Platform (20160712)

@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”

Page 41: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

“Nothing’s the same anymore.”

Babylon 5

Jeffrey Sinclair

Image credit: Astroengine

Page 42: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Legacy: your

customers & money

live here

Page 43: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 44: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Process: scar tissue from past

failure

Page 45: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

“It’s not necessary to change.

Survival is not mandatory.”

—W. Edwards Deming

Page 46: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

The Wall of Confusion (here there be White Walkers)

Page 47: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Page 48: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

the right thing should be

the easy thing

Page 49: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Inaction is still a choice

Page 50: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

12-factor apps need

12-factor ops

Page 51: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

12-factor kitten

Page 52: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

simple patterns automated by

tooling: the cloud native

advantage

Page 53: The Promise of a Cloud Native Platform (20160712)

Cloud Native Infrastructure Automation

@bridgetkromhout

Cloud Native Application Framework

CPI

BOSH release

12 Factor

Cloud Native Contracts

Cloud Native Runtime Platform

Page 54: The Promise of a Cloud Native Platform (20160712)

@bridgetkromhout

Thank you!