Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
@bridgetkromhout
The Promise of a
Cloud Native Platform
Bridget Kromhout
@bridgetkromhout
lives:
Minneapolis,
Minnesota
works:
Pivotal
podcasts:
Arrested
DevOps
organizes:
devopsdays
Bridget Krom...
@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 H...
@bridgetkromhout
Failure: what does recovery look like?
Environments: how long to spin up a
new one or copy an existing on...
@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)
H...
@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...
@bridgetkromhout
@bridgetkromhout
CA
CP AP
AvailabilityConsistency
Partition
Tolerance
“a partition is a
time bound
on communication.”
Eric...
@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 orches...
@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 ...
@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
Clou...
@bridgetkromhout
Thank you!
Upcoming SlideShare
Loading in …5
×

The Promise of a Cloud Native Platform (20160504)

302 views

Published on

http://bridgetkromhout.com/speaking/2016/cloudnativeplatform

Published in: Technology
  • Be the first to comment

  • Be the first to like this

The Promise of a Cloud Native Platform (20160504)

  1. 1. @bridgetkromhout The Promise of a Cloud Native Platform Bridget Kromhout
  2. 2. @bridgetkromhout lives: Minneapolis, Minnesota works: Pivotal podcasts: Arrested DevOps organizes: devopsdays Bridget Kromhout
  3. 3. @bridgetkromhout Image credit: Holly Bailey/Yahoo News
  4. 4. @bridgetkromhout Traded oncall… …for more travel (Similar effect on sleep)
  5. 5. @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
  6. 6. @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?
  7. 7. @bridgetkromhout Not the goal: “automate all the things”
  8. 8. @bridgetkromhout The goal: shorter time from idea to value Image credit: leadliasionImage credit: thebigword
  9. 9. @bridgetkromhout How do we get to the goal?
  10. 10. @bridgetkromhout The Wall of Confusion yolo nope
  11. 11. @bridgetkromhout navigating choices
  12. 12. @bridgetkromhout
  13. 13. @bridgetkromhout devops is practiced, not purchased. Image credit: scriptrock
  14. 14. @bridgetkromhout Land of 10,000 devops clichés
  15. 15. @bridgetkromhout Image credit: xkcd
  16. 16. @bridgetkromhout Docker in Production: Reality, Not Hype
  17. 17. @bridgetkromhout Deconstructing a Python/Django monolith into Dockerized Go microservices (as was the style at the time) How to win at buzzword bingo:
  18. 18. @bridgetkromhout Image credit: James Ernest
  19. 19. @bridgetkromhout Two-Pizza teams
  20. 20. @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
  21. 21. @bridgetkromhout
  22. 22. @bridgetkromhout CA CP AP AvailabilityConsistency Partition Tolerance “a partition is a time bound on communication.” Eric Brewer
  23. 23. @bridgetkromhout Image credit: Vasa Museet
  24. 24. @bridgetkromhout
  25. 25. @bridgetkromhout so what’s a cloud native platform?
  26. 26. @bridgetkromhout Image credit: Simon Wardley
  27. 27. @bridgetkromhout opinions optional if you can deploy and operate code in any capacity, you have a platform
  28. 28. @bridgetkromhout
  29. 29. @bridgetkromhout reasonable constraints
  30. 30. @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
  31. 31. @bridgetkromhout structured contracts determine the promises a platform can keep
  32. 32. @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”
  33. 33. @bridgetkromhout “Nothing’s the same anymore.” Babylon 5 Jeffrey Sinclair Image credit: Astroengine
  34. 34. @bridgetkromhout Legacy: your customers & money live here
  35. 35. @bridgetkromhout Visvesvaraya Museum, Bengaluru IBM 1401 (in use until 1989)
  36. 36. @bridgetkromhout Process: scar tissue from past failure
  37. 37. @bridgetkromhout “It’s not necessary to change. Survival is not mandatory.” —W. Edwards Deming
  38. 38. @bridgetkromhout The Wall of Confusion (here there be White Walkers)
  39. 39. @bridgetkromhout
  40. 40. @bridgetkromhout the right thing should be the easy thing
  41. 41. @bridgetkromhout Inaction is still a choice
  42. 42. @bridgetkromhout 12-factor apps need 12-factor ops
  43. 43. @bridgetkromhout 12-factor kitten
  44. 44. @bridgetkromhout simple patterns automated by tooling: the cloud native advantage
  45. 45. Cloud Native Infrastructure Automation @bridgetkromhout Cloud Native Application Framework CPI BOSH release 12 Factor Cloud Native Contracts Cloud Native Runtime Platform
  46. 46. @bridgetkromhout Thank you!

×