1. serverless:
by Yan Cui
@theburningmonk

3. @theburningmonk theburningmonk.com

4. @theburningmonk theburningmonk.com
hey guys, vote on this post
and I’ll announce a winner at
10PM tonight

5. @theburningmonk theburningmonk.com
10PM
traffic

6. @theburningmonk theburningmonk.com
10PM
traffic
70-100x

7. @theburningmonk theburningmonk.com
system couldn’t fast enough

8. @theburningmonk theburningmonk.com
updates required 30 mins downtime

9. @theburningmonk theburningmonk.com
features took months to deliver

10. @theburningmonk theburningmonk.com
Dan North
“lead time to someone saying thank you is the
only reputation metric that matters.”

11. @theburningmonk theburningmonk.com
6 months, 6 devs

12. @theburningmonk theburningmonk.com
95% cost saving compared to existing EC2-based solution

13. @theburningmonk theburningmonk.com
velocity went from months to days

14. @theburningmonk theburningmonk.com
https://www.youtube.com/watch?v=evsz__BDprs

15. @theburningmonk theburningmonk.com
https://www.youtube.com/watch?v=evsz__BDprs
AppSync
DynamoDB
Lambda

16. Yan Cui
http://theburningmonk.com
@theburningmonk
AWS user for 10 years

17. Yan Cui
http://theburningmonk.com
@theburningmonk
http://bit.ly/yubl-serverless

18. Yan Cui
http://theburningmonk.com
@theburningmonk
Developer Advocate @

20. Yan Cui
http://theburningmonk.com
@theburningmonk
Independent Consultant
advisetraining delivery

21. theburningmonk.com/courses

22. theburningmonk.com/courses

23. realworldserverless.com

24. @theburningmonk theburningmonk.com
2010

25. @theburningmonk theburningmonk.com

26. @theburningmonk theburningmonk.com

27. @theburningmonk theburningmonk.com
users are distributed
around the world
systems have to be
available 24/7

28. @theburningmonk theburningmonk.com
millions of unique daily-active users

30. SCALABILITY

31. SCALABILITY
RESILIENCE

32. SCALABILITY
RESILIENCE
SECURITY

33. SCALABILITY
RESILIENCE
SECURITY
SPEED

34. @theburningmonk theburningmonk.com

36. @theburningmonk theburningmonk.com
networking
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups

37. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up multi-AZ
set up load balancer
configure IAM roles
set up logging agent
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups

38. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up multi-AZ
set up load balancer
configure IAM roles
set up logging agent
application
set up web server
configure middlewares
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups

39. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up multi-AZ
set up load balancer
configure IAM roles
set up logging agent
application
set up web server
configure middlewares
write 1st line of
business logic
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups

40. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up multi-AZ
set up load balancer
configure IAM roles
set up logging agent
application
set up web server
configure middlewares
write 1st line of
business logic
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups
the only thing the
customer cares about!

41. @theburningmonk theburningmonk.com

42. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up multi-AZ
set up load balancer
configure IAM roles
set up logging agent
application
set up web server
configure middlewares
write 1st line of
business logic
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups

43. @theburningmonk theburningmonk.com
networking VMs
apply patches
install dependencies
create base AMI
set up auto-scaling
set up load balancer
configure IAM roles
set up logging agent
application
set up web server
configure middlewares
write 1st line of
business logic
set up VPC
set up public subnet
set up private subnet
set up Internet Gateway
set up NAT Gateway
configure Route Tables
configure Network ACL
configure Security Groups
mooooo..

44. @theburningmonk theburningmonk.com
but, nonetheless… they’re important for setting you up to succeed

45. @theburningmonk theburningmonk.com
spinning up a web-server a production-ready environment!===

46. @theburningmonk theburningmonk.com
“we ain’t gonna need it”

47. @theburningmonk theburningmonk.com
“we ain’t gonna need it”
translation: “we will never be successful”

48. @theburningmonk theburningmonk.com
traffic
holy crap, we’ve
got traction!

49. @theburningmonk theburningmonk.com
traffic
oh no… our server died!

50. @theburningmonk theburningmonk.com
prepare for success

51. @theburningmonk theburningmonk.com
isn’t the savior?

52. @theburningmonk theburningmonk.com
0
Theory
“it works on
my machine!”
“production
ready!”days

53. @theburningmonk theburningmonk.com

54. @theburningmonk theburningmonk.com

55. @theburningmonk theburningmonk.com

56. @theburningmonk theburningmonk.com
0
Theory
“it works on
my machine!”
“production
ready!”
0
Reality
“it works on
my machine!”
“production
ready!”
days
days

57. @theburningmonk theburningmonk.com

58. @theburningmonk theburningmonk.com
mooooo..

59. @theburningmonk theburningmonk.com
scale

60. @theburningmonk theburningmonk.com
scale complexity

61. @theburningmonk theburningmonk.com
but our cognitive capacity hasn’t increased…

62. @theburningmonk theburningmonk.com
leverage: do more with less

63. @theburningmonk theburningmonk.com
EC2
EC2

64. @theburningmonk theburningmonk.com
EC2
EC2
we’re still managing
infrastructure

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

66. @theburningmonk theburningmonk.com
infrastructure
you

67. @theburningmonk theburningmonk.com
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

68. @theburningmonk theburningmonk.com
“Serverless”

69. @theburningmonk theburningmonk.com

70. @theburningmonk theburningmonk.com
Gojko Adzic
It is serverless the same way
WiFi is wireless.
http://bit.ly/2yQgwwb

71. @theburningmonk theburningmonk.com
“Function-as-a-Service”
AWS Lambda
Azure Functions
Google Cloud Functions
Auth0 Webtask
Spotinst Functions Kubeless
IBM Cloud Functions

72. AWS Lambda

73. AWS Lambda
API Gateway IOT SNS Kinesis CloudWatch

74. @theburningmonk theburningmonk.com
Why serverless?

75. @theburningmonk theburningmonk.com
more Scalable

76. @theburningmonk theburningmonk.com
100% SERVERLESS
IN PRODUCTION

77. @theburningmonk theburningmonk.com

78. @theburningmonk theburningmonk.com
80 MILLION
MONTHLY USERS

79. @theburningmonk theburningmonk.com

80. @theburningmonk theburningmonk.com
Cheaper
(don’t pay for idle servers)

81. @theburningmonk theburningmonk.com
Resilience
(built-in redundancy and multi-AZ)

82. @theburningmonk theburningmonk.com
Secure

83. @theburningmonk theburningmonk.com
idea production
amazing VELOCITY from idea to product

84. @theburningmonk theburningmonk.com
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

85. @theburningmonk theburningmonk.com
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

86. @theburningmonk theburningmonk.com
truly “fullstack” developers are rare, and expensive

87. @theburningmonk theburningmonk.com
AWS
Scalability
Resilience
Security
DevOps
Distributed
Systems
JavaScript
CSS
HTML
SPA Framework
Responsive
Design
Debugging

88. @theburningmonk theburningmonk.com
AWS
Scalability
Resilience
Security
DevOps
Distributed
Systems
JavaScript
CSS
HTML
SPA Framework
Responsive
Design
Debugging

89. @theburningmonk theburningmonk.com
AWS
Scalability
Resilience
Security
DevOps
Distributed
Systems
JavaScript
CSS
HTML
SPA Framework
Responsive
Design
Debugging

90. @theburningmonk theburningmonk.com
AWS
Scalability
Resilience
Security
DevOps
Distributed
Systems
JavaScript
CSS
HTML
SPA Framework
Responsive
Design
Debugging

91. @theburningmonk theburningmonk.com
what you need to know to build a production-ready backend on AWS
EC2 / Containers Serverless

92. @theburningmonk theburningmonk.com
what you need to know to build a production-ready backend on AWS
EC2 / Containers Serverless

93. @theburningmonk theburningmonk.com
what you need to know to build a production-ready backend on AWS
EC2 / Containers Serverless

94. @theburningmonk theburningmonk.com
frontend focused teams can delay the point when they need a backend specialist

95. @theburningmonk theburningmonk.com
backend engineers can get so much more done with less effort and stress

96. @theburningmonk theburningmonk.com
https://www.youtube.com/watch?v=evsz__BDprs

97. @theburningmonk theburningmonk.com
what you need to know to build a production-ready backend on AWS
EC2 / Containers Serverless
AWS basics, DynamoDB,
Lambda, SNS, etc.

98. @theburningmonk theburningmonk.com
AppSync
DynamoDB
Lambda
ElasticSearch

99. @theburningmonk theburningmonk.com
focus your time and energy on improving the UX

100. @theburningmonk theburningmonk.com
the backend should “just work”

101. @theburningmonk theburningmonk.com
the backend should “just work”
it shouldn’t be THAT hard, and it doesn’t have to

102. @theburningmonk theburningmonk.com

103. @theburningmonk theburningmonk.com
don’t use callbacks, use async-await

104. @theburningmonk theburningmonk.com
avoid mixing callbacks with Promises

105. @theburningmonk theburningmonk.com
too sequential

106. @theburningmonk theburningmonk.com
missing Promise.all

107. @theburningmonk theburningmonk.com
async-await in forEach

108. @theburningmonk theburningmonk.com
not useing AWS SDK’s .promise()

109. cold starts

110. @theburningmonk theburningmonk.com
INITIALISE
CONTAINER
INITIALISE
RUNTIME
INITIALISE
HANDLER
YOUR CODE
EXECUTES

111. @theburningmonk theburningmonk.com
INITIALISE
CONTAINER
INITIALISE
RUNTIME
INITIALISE
HANDLER
YOUR CODE
EXECUTES
COLD START

112. @theburningmonk theburningmonk.com
“cold starts only happen to the first request”

113. @theburningmonk theburningmonk.com
function invocationconcurrent execution
i.e. a container

114. @theburningmonk theburningmonk.com
function invocationconcurrent execution
i.e. a container
class instance method call

115. @theburningmonk theburningmonk.com
Lambda scales the number of concurrent executions based on traffic

116. @theburningmonk theburningmonk.com
existing “containers” are reused where possible

117. @theburningmonk theburningmonk.com
time
invocation

118. @theburningmonk theburningmonk.com
time
invocation
invocation

119. @theburningmonk theburningmonk.com
time
invocation
invocation

120. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation

121. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation

122. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation

123. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation
invocation

124. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation
invocation invocation

125. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation
invocation invocation

126. @theburningmonk theburningmonk.com
time
invocation
invocation
invocation
invocation
invocation
invocation
invocation invocation

127. @theburningmonk theburningmonk.com

128. @theburningmonk theburningmonk.com

129. @theburningmonk theburningmonk.com

130. @theburningmonk theburningmonk.com

131. @theburningmonk theburningmonk.com
FREQUENCY DURATION

132. @theburningmonk theburningmonk.com
FREQUENCY DURATION
dictated by user traffic,
out of your control

133. @theburningmonk theburningmonk.com
FREQUENCY DURATION
optimize this!

134. @theburningmonk theburningmonk.com
if you need good cold start performance
DON’T run express.js in a Lambda

135. @theburningmonk theburningmonk.com
“Lambda is not a suitable solution for me because of cold starts”

136. @theburningmonk theburningmonk.com
“what is your latency requirement?”

137. @theburningmonk theburningmonk.com
cold starts that don’t add to user-facing latency is
generally not worth worrying about

138. @theburningmonk theburningmonk.com
sporadic spikes latency existed before Lambda

139. @theburningmonk theburningmonk.com
GC pauses…

140. @theburningmonk theburningmonk.com
overloaded servers…

141. @theburningmonk theburningmonk.com
slow downstream, databases, etc.

142. @theburningmonk theburningmonk.com
networking issues…

143. @theburningmonk theburningmonk.com
cold starts is generally not an issue if you have a steady traffic pattern

144. @theburningmonk theburningmonk.com
time
req/s

145. @theburningmonk theburningmonk.com
time
req/s
El Classico

146. @theburningmonk theburningmonk.com
time
req/s
lunch dinner

147. @theburningmonk theburningmonk.com
minimise the duration of cold starts so they
fall within acceptable latency range

148. @theburningmonk theburningmonk.com
require specific clients instead of the full AWS SDK

149. @theburningmonk theburningmonk.com
use webpack to bundle functions during deployment

150. @theburningmonk theburningmonk.com

151. @theburningmonk theburningmonk.com
then, consider using Provisioned Concurrency as a fallback

152. @theburningmonk theburningmonk.com
time
req/s
lunch dinner
Provisioned
Concurrency

153. @theburningmonk theburningmonk.com
time
req/s
lunch dinner
Provisioned
Concurrency
On-Demand
Concurrency

154. @theburningmonk theburningmonk.com
there are no silver bullets

155. @theburningmonk theburningmonk.com
Provisioned Concurrency is a powerful tool
IFF you have a cold start problem
DON’T use it by default

157. theburningmonk.com/hire-me
AdviseTraining Delivery
“Fundamentally, Yan has improved our team by increasing our
ability to derive value from AWS and Lambda in particular.”
Nick Blair
Tech Lead

158. homeschool.dev/class/production-ready-serverless
15% OFF WITH “YANPRS15”

159. @theburningmonk
theburningmonk.com
github.com/theburningmonk
159