The document discusses the promise of cloud native platforms for enabling faster development and deployment. It notes that cloud native platforms provide standardized contracts and constraints that allow applications to be deployed predictably in any infrastructure capacity, while also promoting automation through simple patterns that can be easily managed by tools. By adopting cloud native approaches like containerization and immutable infrastructure, organizations can reduce the time between developing an idea and releasing value to customers.

1. @bridgetkromhout
The Promise of a
Cloud Native Platform
Bridget Kromhout

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

3. @bridgetkromhout
Traded oncall… …for more travel (Similar effect on sleep)

4. @bridgetkromhout
“In the last week there were
67 deploys
of 496 changes
by 18 people”
Image credit: visual_dichotomy on Flickr

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. @bridgetkromhout
Why don’t we all move that fast today?

7. @bridgetkromhout
Environments: how long to spin up a
new one or copy an existing one?
Why don’t we all move that fast today?

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

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

10. @bridgetkromhout
Not the goal:
“automate all the things”

11. @bridgetkromhout
The goal: shorter time from
idea to value
Image credit: leadliasionImage credit: thebigword

12. @bridgetkromhout
How do we
get to
the goal?

13. @bridgetkromhout
How do we
get to
the goal?

14. @bridgetkromhout
The Wall of Confusion

15. @bridgetkromhout
The Wall of Confusion
yolo nope

16. @bridgetkromhout
navigating
choices

17. @bridgetkromhout

18. @bridgetkromhout
devops is
practiced,
not
purchased.
Image credit: scriptrock

19. @bridgetkromhout
Land of 10,000 devops clichés

20. @bridgetkromhout
Image credit: xkcd

21. @bridgetkromhout
Docker in Production:
Reality, Not Hype

22. @bridgetkromhout
Deconstructing a
Python/Django
monolith into
Dockerized
Go microservices
(as was the style
at the time)
How to win at buzzword bingo:

23. @bridgetkromhout

24. @bridgetkromhout
Image credit: James Ernest

25. @bridgetkromhout
Two-Pizza
teams

26. @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

27. @bridgetkromhout
“Effective
devops tools
enable automation
without
isolating humans
from the automation
process”
Jennifer Davis

28. @bridgetkromhout

29. @bridgetkromhout
CA
CP AP
AvailabilityConsistency
Partition
Tolerance
“a partition is a
time bound
on communication.”
Eric Brewer

30. @bridgetkromhout
Image credit: Vasa Museet

31. @bridgetkromhout

32. @bridgetkromhout
so what’s a
cloud
native
platform?

33. @bridgetkromhout
Image credit: Simon Wardley

34. @bridgetkromhout
if you can deploy and operate
code in any capacity, you
have a platform

35. @bridgetkromhout
opinions optional
if you can deploy and operate
code in any capacity, you
have a platform

36. @bridgetkromhout

37. @bridgetkromhout
reasonable
constraints

38. @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

39. @bridgetkromhout
structured contracts
determine the promises
a platform can keep

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

41. @bridgetkromhout
“Nothing’s the same anymore.”
Babylon 5
Jeffrey Sinclair
Image credit: Astroengine

42. @bridgetkromhout
Legacy:
your
customers
& money
live
here

43. @bridgetkromhout

44. @bridgetkromhout
Process:
scar tissue
from past
failure

45. @bridgetkromhout
“It’s not necessary
to change.
Survival is
not mandatory.”
—W. Edwards
Deming

46. @bridgetkromhout
The Wall of Confusion (here there be White Walkers)

47. @bridgetkromhout

48. @bridgetkromhout
the right thing
should be
the easy thing

49. @bridgetkromhout
Inaction is still a choice

50. @bridgetkromhout
12-factor apps
need
12-factor ops

51. @bridgetkromhout
12-factor
kitten

52. @bridgetkromhout
simple patterns
automated by
tooling:
the cloud native
advantage

53. Cloud Native Infrastructure Automation
@bridgetkromhout
Cloud Native Application Framework
CPI
BOSH release
12 Factor
Cloud Native Contracts
Cloud Native Runtime Platform

54. @bridgetkromhout
Thank you!