In this talk, we discussed why businesses should care about serverless and why it's not just a tool for developers.

1. A WIN
FOR
DEVELOPERS
NOT
JUST
BUSINESSES
serverless:

3. the why of technology is to
solve business problems and
create business values

4. my job as an engineer is NOT to write code

5. the code is not the product

6. the code is not the product
it’s a cost, a means to an end

7. my job as an engineer is to create value

8. what is the biggest challenge
facing your company?

9. finding market fit

10. runway

11. runway: f(investment, cost) => time

12. John Richard Boyd
US air force colonel
“Fighter Pilot who changed the Art of War”

13. OODA loop

14. Observe
OODA loop
collect data

15. Observe Orient
OODA loop
collect data analyse data,
form metal model

16. Observe Orient Decide
OODA loop
collect data analyse data,
form metal model
decide course
of action

17. Observe Orient Decide Act
OODA loop
collect data analyse data,
form metal model
decide course
of action
action!

18. Observe Orient Decide Act
OODA loop
collect data analyse data,
form metal model
decide course
of action
action!

19. Observe Orient Decide Act
OODA loop
product development

20. Observe Orient Decide Act
OODA loop
Understand
product development

21. Observe Orient Decide Act
OODA loop
Understand Define
product development

22. Observe Orient Decide Act
OODA loop
Understand Define Design
product development

23. Observe Orient Decide Act
OODA loop
Understand Define Design Deliver
product development

24. Boyd’s Law of Iteration
Boyd decided that the primary determinant to winning dogfights
was not observing, orienting, planning, or acting better. The primary
determinant to winning dogfights was observing, orienting,
planning, and acting faster. In other words, how quickly one could
iterate. Speed of iteration, Boyd suggested, beats quality of iteration.

25. Boyd’s Law of Iteration
Boyd decided that the primary determinant to winning dogfights
was not observing, orienting, planning, or acting better. The primary
determinant to winning dogfights was observing, orienting,
planning, and acting faster. In other words, how quickly one could
iterate. Speed of iteration, Boyd suggested, beats quality of iteration.Speed of iteration, Boyd suggested, beats quality of iteration.

27. runway

28. runway

30. communication overhead

31. communication overhead
inter-team dependencies

32. communication overhead
inter-team dependencies
lack of autonomy

33. Yan Cui
http://theburningmonk.com
@theburningmonk
Independent Consultant
Advisor @
Instructor @
Instructor @

34. AWS user since 2009

35. AWS user since 2009

36. 2006

37. big meetings to decide how to provision new servers

38. 3-6 months (!!!!) turn around time

39. client tier
logic tier
data tier
SQL

40. monolithic, 3-tier architectures

41. requires downtime for deployment

42. requires downtime for deployment
(OK for businesses that aren’t 24/7)

44. big-bang releases

45. 2010

46. on premise cloud

47. EC2
EC2

48. EC2
EC2
months minutes

49. EC2
EC2
months minutes

50. EC2
EC2
minutes
compute becoming a commodity
Genesis Custom-built Product Commodity
http://bit.ly/wardley-maps

51. EC2
EC2
minutes

54. users are distributed
around the world
systems have to be
available 24/7

56. SCALABILITY

57. SCALABILITY
RESILIENCE

58. SCALABILITY
RESILIENCE
SECURITY

59. SCALABILITY
RESILIENCE
SECURITY
SPEED

61. Capex Opex
capital expenditure operational expenditure

62. Capex Opex
capital expenditure operational expenditure
levelled the playing field

63. competition

64. competition user demand &
expectations

66. faster delivery
faster feedback loop
we need…

68. big-bang releases small, frequent releases

70. co-evolution
waterfall agile
silos DevOps
practice
activity
of
and

71. scale

72. scale complexity

73. but our cognitive capacity hasn’t increased…

74. leverage: do more with less

75. EC2
EC2

76. EC2
EC2
we’re still managing
infrastructure

77. https://bit.ly/2Im61VK
“Unless you’re an infrastructure company,
infrastructure is basically overhead.”
Matt Klein

78. infrastructure
you

79. EC2EC2
EC2 RDSDynamoDB SQS

81. Monoliths Microservices

82. EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB

83. EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB
we’re managing
lots more
infrastructure!

84. we need a better abstraction for the “server”

85. we need an immutable infrastructure

86. 70% utilization
monolith
10% utilization
x 10
microservices

87. 70% utilization
monolith
10% utilization
x 10
microservices

89. 0
Theory
“it works on
my machine!”
“production
ready!”days

93. 0
Theory
“it works on
my machine!”
“production
ready!”
0
Reality
“it works on
my machine!”
“production
ready!”
days
days

95. mooooo..

96. runway

97. runway
how do we optimize the runway
to get more iterations out of it?

99. runway
we need cheaper and
lighter planes!

100. 2016

101. 2016

102. Server-ful Serverless

103. 2016
95% cost saving vs EC2

104. 2016
95% cost saving vs EC2
15x number of production deploys

105. 2016
95% cost saving vs EC2
15x number of production deploys
same sized team

107. minimise undifferentiated
heavy-lifting

108. Why serverless?

109. more Scalable

110. Cheaper
(don’t pay for idle servers)

111. 2016
95% cost saving vs EC2

112. https://aws.amazon.com/solutions/case-studies/financial-engines/

113. https://www.doc.ic.ac.uk/~rbc/papers/fse-serverless-17.pdf
“This paper presents two
case industrial studies of
early adopters, showing
how migrating an
application to the
Lambda deployment
architecture reduced
hosting costs – by
between 66% and 95%…”

116. Resilience
(built-in redundancy and multi-AZ)

117. http://bit.ly/2Vzfexo

118. Secure

119. Shared Responsibility Model

120. protection from OS attacks
Amazon automatically apply latest patches to host VMs

123. request
blue-green deployment
req/s
auto-scaling
us-east-1a
us-east-1b
us-east-1c
multi-AZ

124. the DevOps forcethe DevOps force
is strong with serverlessis strong with serverless

125. idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
configure
autoscaling
capacity planning
over-provision for
launch
are we doing
microservices?
configure CI/CD

126. idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
configure
autoscaling
capacity planning
over-provision for
launch
are we doing
microservices?
configure CI/CD

127. idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
configure
autoscaling
capacity planning
over-provision for
launch
are we doing
microservices?
configure CI/CD

128. idea production
greater Velocity from idea to product

129. 2016
15x number of production deploys
same sized team

130. leverage: do more with less

131. focus on customer needs

132. https://bit.ly/2Im61VK
“Unless you’re an infrastructure company,
infrastructure is basically overhead.”
Matt Klein

133. building a resilient, and scalable
infrastructure is hard work

134. building a resilient, and scalable
infrastructure is hard work
and crucial to
your success!

135. diverts attention from core
business problems

136. creates inter-team dependency

137. leading to delays, and time
pressure and stress

138. serverless teams are smaller,
and happier!

139. smaller teams
less comm overhead
fewer meetings
more time getting stuff done!

142. developers are able to own more of
their stack

143. developers are able to own more of
their stack
more autonomy

144. leverage: do more with less

145. cheaper, lighter, go faster

146. competition waits for no one