Serverless is all the rage these days, but how did we get here and why should businesses and developer care about serverless? In this talk, we will hear about Yan's journey from running on-prem servers to EC2, to containers, and finally to serverless. We will hear about the evolution of development practices and debunk some common misconceptions about serverless. We'll also get a glimpse of how we can build new kinds of businesses on top of serverless, and why FinDev might be an even bigger game changer for businesses than DevOps.

1. HOW
DID WE
HEADED
WHERE
AREWE
HEREGET
serverless:

2. Yan Cui
http://theburningmonk.com
@theburningmonk
Principal Engineer @
Independent Consultant

5. available in Austria, Switzerland, Germany,
Japan, Canada, Italy, US and Spain

6. available on 30+ platforms

7. ~1,000,000 concurrent viewers

8. follow @dazneng for
updates about the
engineering team
We’re hiring! Visit
engineering.dazn.com
to learn more.
WE’RE HIRING!

9. AWS user since 2009

10. AWS user since 2009

12. 2006

13. big meetings to decide how to provision new servers

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

15. client tier
logic tier
data tier
SQL

16. monolithic, 3-tier architectures

17. requires downtime for deployment

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

19. install monitoring agents/daemons on server

21. big-bang releases

22. 2010

23. on premise cloud

24. 2012

25. 2016

26. 2019

27. EC2
EC2

28. EC2
EC2
months minutes

29. EC2
EC2
months minutes

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

31. EC2
EC2
minutes

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

36. SCALABILITY

37. SCALABILITY
RESILIENCE

38. SCALABILITY
RESILIENCE
SECURITY

39. SCALABILITY
RESILIENCE
SECURITY
SPEED

41. Capex Opex
capital expenditure operational expenditure

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

43. competition

44. competition user demand &
expectations

46. faster delivery
faster feedback loop
we need…

48. big-bang releases small, frequent releases

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

51. scale

52. scale complexity

53. but our cognitive capacity hasn’t increased…

54. leverage: do more with less

55. EC2
EC2

56. EC2
EC2
we’re still managing
infrastructure

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

58. infrastructure
you

59. EC2EC2
EC2 RDSDynamoDB SQS

61. Monoliths Microservices

62. EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB

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

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

65. we need an immutable infrastructure

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

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

69. EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB

70. EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB
DynamoDB
RDS
SQS DynamoDB

71. EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB
DynamoDB
RDS
SQS DynamoDB

72. EC2 docker
us-east-1a us-east-1b
us-east-1a us-east-1b

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

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

79. mooooo..

80. 2016

81. SQL NoSQL
OOP Functional
On Premise Cloud
Waterfall Agile
Monoliths Microservices

82. 2016

83. 2016

84. Server-ful Serverless

85. https://gtnr.it/2KGyGCM

87. What do you mean
by ‘serverless’?

88. “Serverless”

90. Gojko Adzic
It is serverless the same way
WiFi is wireless.
http://bit.ly/2yQgwwb

91. Serverless means…
don’t pay for it if no-one uses it
don’t need to worry about scaling
don’t need to provision and manage servers

92. “Function-as-a-Service”
AWS Lambda
Azure Functions
Google Cloud Functions
Auth0 Webtask
Spotinst Functions Kubeless
IBM Cloud Functions

93. AWS Lambda

94. AWS Lambda
API Gateway IOT SNS Kinesis CloudWatch

95. IaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
CaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
PaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
FaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
User User (scalable unit) Provider

96. IaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
CaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
PaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
FaaS
Function
Application
Runtime
Container
OS
Virtualization
Hardware
User User (scalable unit) Provider

97. Serverless
FaaS
other services…
Database
Storage
BI

98. Simon Wardley
Serverless will fundamentally change
how we build business around
technology and how you code.

99. Why serverless?

100. more Scalable

101. 1,000 concurrent executions (soft limit)
500 increase per minute (hard-ish limit)

102. 1,000 concurrent executions (soft limit)
500 increase per minute (hard-ish limit)
AUTO-APPROVED
RAISE TO 3000

103. 1,000 concurrent executions (soft limit)
500 increase per minute (hard-ish limit)

104. containers are reused

105. 100% SERVERLESS
IN PRODUCTION

106. 80 MILLION
MONTHLY USERS

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

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

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

110. Secure

111. Shared Responsibility Model

112. Shared Responsibility Model

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

116. Deploy

117. serverless.yml
{}
Code

118. {}
Code
serverless.yml

119. serverless.yml
{}
Code
S3

120. {}
Code
serverless.yml
S3 CloudFormation

121. {}
Code
serverless.yml
S3 CloudFormation

122. request
blue-green deployment

123. request
blue-green deployment

124. request
blue-green deployment

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

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

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

129. idea production
greater Velocity from idea to product

130. minimise undifferentiated
heavy-lifting

131. less ops responsibility on
your shoulders

132. infrastructure
you

133. DynamoDBDynamoDB
RDS
SQS DynamoDB
DynamoDB
API Gateway Lambda
API Gateway Lambda RDS
Lambda DynamoDBSQS

134. abstractionlayer

135. abstractionlayer
paradigm
shift!!!!

136. paradigm shift

137. paradigm shift
opportunity

138. performance
time
serverless
containers

139. performance
time
serverless
containers
higher ceiling

140. speed

141. performance
time
serverless
containers
higher ceiling
strong baseline

142. performance
time
serverless
containers
dilemma
zone

143. paradigm shift
opportunity
challenges

144. broken existing toolchains

145. observability securityframework

146. best practices are still emerging

147. ๏ tips for writing Lambda functions
๏ migration to serverless
๏ serverless ops
๏ design patterns
๏ performance optimization
๏ chaos engineering
๏ security
๏ general thoughts and techniques
http://bit.ly/theburningmonk-serverless

148. https://bit.ly/production-ready-serverless

149. is serverless production-ready?

152. 2018

154. 1,000 concurrent executions (soft limit)
500 increase per minute (hard-ish limit)

156. ~1,000,000 concurrent viewers

158. serverless is not right for every use case (yet)

159. http://bit.ly/2WSfcky

160. Lambda VPC

161. there are no silver bullets

163. 0
Containers
“it works on
my machine!”
“production
ready!”days
Serverless
0
“it works!”
“production
ready!”
days

164. 0
Containers
“it works on
my machine!”
“production
ready!”days
Serverless
0
“it works!”
“production
ready!”
days
v2! v3! v4! v5! v6!

165. EC2 docker
us-east-1a us-east-1b
us-east-1a us-east-1b
Theory

166. Reality

167. Reality

168. scale-to-zero

169. serverful serverless
us-east-1a us-east-1b
us-east-1a us-east-1bscaled to zero!

170. HOW
DID WE
HEREGET
serverless:

171. HEADED
WHERE
AREWE
serverless:

172. scaling limits VPC long-running
cold starts performance

173. scaling limits VPC long-running
cold starts performance

174. scaling limits VPC long-running
cold starts performance

175. http://bit.ly/2X0ksCY

176. http://bit.ly/2X0ksCY

177. http://bit.ly/2X0ksCY

178. scaling limits VPC long-running
cold starts performance

179. http://bit.ly/2I7GJeJ

180. scaling limits VPC long-running
cold starts performance

182. scaling limits VPC long-running
cold starts performance

184. + pay-per-use?

185. Simon Wardley
Serverless will fundamentally change
how we build business around
technology and how you code.

186. @theburningmonk
theburningmonk.com
github.com/theburningmonk