This document discusses the concepts of cloud native development. It begins by discussing how organizations like Netflix and Amazon deploy code continuously using automation platforms. It then discusses how cloud native principles like microservices, infrastructure as code, and continuous delivery can be applied using tools and platforms to build software. The document advocates for building cloud native culture within organizations through high trust, learning, and empowering teams.

1. your cloud native future
Andrew Clay Shafer

3. you have to be serious

4. you can’t be so irreverent

5. do you have to be so serious?

6. you are a zealot

10. Humans are allergic to change. They love to say,
"We've always done it this way." I try to fight that.

11. It is not necessary to change.
Survival is not mandatory.
- W. Edwards Deming

12. Andrew Clay Shafer

13. Andrew Clay Shafer
@littleidea

14. Andrew Clay Shafer
@littleidea

15. @littleidea

16. software is eating the world

17. insurmountable opportunity

18. transform human experience

19. transform human performance

20. you are building a
software business
or losing to someone who is

21. you are building software
or losing to someone who is

22. talks I am not giving today…

23. devops, managing complex
systems at scale

24. building for failure and MTTR

25. configuration services, service
discovery, and circuit breakers

26. continuous delivery,
microservices and you

27. faster and safer
BLAH BLAH BLAH BLAH
OODA LOOP
SMALL BATCHES

28. three stone cutters walk into a
Pareto Inefficient Nash Equilibrium

29. Three Stone Cutters
What do you do?

30. I get paid
to cut stones

31. I am an
expert craftsmen.

33. I build cathedrals.

34. In Conclusion…

35. you are building a
learning organization
or losing to someone who is

36. Software is Eating the World

37. BS
Software just all of a sudden got hungry?

38. what is disrupting everything are
the experiences being created

39. super computers in every
pocket connected to each other
and all human knowledge by
high speed networks

40. every aspect of human performance
and experience that can be optimized
will be

41. what is the solution?

42. let’s talk about #winning

43. tale of two software projects

47. It was supposed to be a "killer app," but a system deployed to
volunteers by Mitt Romney's presidential campaign may have
done more harm to Romney's chances on Election Day

48. Aurich Lawson / Thinkstock

49. if you don’t experiment before
putting things into production
production is always an experiment

50. might have lost the election

51. but Harper is an unicorn,
we don’t have the talent

52. “Netflix hired them from you,
and got out of their way.”

53. Principles > Practices >Tools

54. why > what

55. success and failure are
correlated with learning

56. software is creating experiences

57. software is creative

58. software is complex

59. software is prone to failure

60. software is not digging ditches

61. software is closer to art than science

62. software is a socio-technical
evolution of our capabilities

63. to succeed at software you
need the capacity to create

64. to succeed at software you
need to be willing to fail

65. you are building a
learning organization
or losing to someone who is

66. you haven’t learned anything
until you change your behavior

67. devops,
platforms,
continuous delivery,
microservices…

68. These things
are all one…

69. same patterns emerged in high
performing organizations that
deliver highly available
applications continuously at scale

70. from now on, I’m going to call all
that together… ‘Cloud Native’

71. –Leo Devops Tolstoy
“All happy applications are alike;
each unhappy application is unhappy in its own way.”

72. what would cloud natives do?
wwcnd

73. Amazon, a bookstore in Seattle, deploys
code to production every 11 seconds…
1 second

74. –Werner Vogels, CTO Amazon
“The traditional model is that you take your software to the wall
that separates development and operations, and throw it over
and then forget about it. Not at Amazon. You build it, you run it.
This brings developers into contact with the day-to-day
operation of their software. It also brings them into day-to-day
contact with the customer. This customer feedback loop is
essential for improving the quality of the service.”

75. Adrian Cockroft - ex-Netflix
What I learned from my time at Netflix.

76. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant

77. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant

78. Netflix built a platform to enable
self service deployment

79. Netflix built a platform to deploy
and operate microservices

80. Netflix built a platform to
continuously deliver software

81. Netflix built a platform that could
protect itself from failure

82. What Netflix did not do is build a platform
for general ad-hoc automation…

83. Constraints are the contract that
allows a platform to keep
promises.

84. Everyone has a platform.
What promises can
your platform keep?

85. Cloud Foundry promises
starts at the API

86. API all the things

87. •current_vm_id
•create_stemcell
•delete_stemcell
•create_vm
•delete_vm
•has_vm?
•reboot_vm
•set_vm_metadata
•configure_networks
•create_disk
•delete_disk
•attach_disk
•snapshot_disk
•delete_snapshot
•detach_disk
•get_disks
Cloud Provider Interface

88. Cloud Native Infrastructure Automation
CPI

89. need to manage a large distributed system
• deployment
• configuration changes
• updates/upgrades - minimal downtime
• health checks and remediation
• scale out/scale in
• across multiple IaaS

90. Everything as a Service

91. Now that we have a tool chain for
release engineering, deployment,
and lifecycle management of large-
scale distributed services…
What should we do with it?

92. deploy a self-service self-healing
container scheduler, of course!

93. routers
Linux
LinuxLinux
Containers
message bus
cloud controller
loggregators
controller DB
etcd
hm9000
metrics firehose
UAA
login
Cloud Foundry Elastic Runtime
service
brokers
object
store
stagers

94. Cloud Native Runtime Platform
Cloud Native Infrastructure Automation
CPI
BOSH release

95. • role based access to resources
• run code on demand
• coordinate cross service
configurations
• route public requests
• read and write persistent data
• add and remove resources
• record internal and external
events
• isolate resources and failures
• measure performance/health
• detect and determine failure
(plan & provoke failure)
• recover failures
• work tomorrow
What problems does it solve?

96. 12 Factor Ops

97. your pipeline to continuously
deliver microservices is ready
(and win buzzword bingo)

98. cloud native application:
• 12 factor contract
• composable
• discoverable
• fault tolerant

99. •I. Codebase
•II. Dependencies
•III. Config
•IV. Backing Services
•Build, release, run
•VI. Processes
•VII. Port binding
•VIII. Concurrency
•IX. Disposability
•X. Dev/prod parity
•XI. Logs
•XII. Admin processes

100. ‘boot’ makes microservices easy
‘cloud’ provides composable patterns

101. • configuration service
• service registry
• service discovery
• client load balancing
• circuit breaker
• micro-proxy
• api gateways

102. If you are one of those people who like to read books…

103. The Stories We Tell

104. the patterns proven successful
building and operating highly
available systems with predictable
scaling and failure characteristics

105. Cloud Native Runtime Platform
Cloud Native Infrastructure Automation
Cloud Native Application Framework
CPI
BOSH release
12 Factor
Cloud Native Contracts

106. structured contracts
determine the promises a
platform can keep

107. simple patterns
automated by tooling

108. simple patterns
automated by tooling

109. simple patterns
automated by tooling

110. Use tools and simple
patterns to make doing the
right thing the easy thing

111. high trust, low process,
no hand-offs between teams
freedom and responsibility

112. Cloud Native Runtime Platform
Cloud Native Infrastructure Automation
Cloud Native Application Framework
CPI
BOSH release
12 Factor
Cloud Native Contracts
Cloud Native Culture

113. how many put as much effort into
designing their culture as they do
their applications and systems?

114. This is the
cloud native
advantage

115. This is what helps
organizations move
quickly at scale

116. Motivated to change the relationship
between people and the computers
I never set out to DO devops.

117. actually, needed to change the
relationship between people and people

118. no one originally set out to do devops,
continuous delivery, microservices, or
platforms these were natural consequences
don’t fixate on the words, fixate on the outcomes

119. if you want to align people in your
organization, think about the
interfaces, look at the promises they
make and keep with each other.

120. what do you do?

121. I build the future

122. and so can you

123. the future is already here
it’s just not evenly distributed
- William Gibson

124. Thank You
@littleidea

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