1. SERVERLESS DESIGN PATTERNS

2. 2014

8. “Serverless”

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

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

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

13. AWS Lambda

14. AWS Lambda
API Gateway IOT SNS Kinesis CloudWatch

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

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

17. Serverless
FaaS
other
Database
Storage
BI

18. SERVERLESS WILL FUNDAMENTALLY
CHANGE HOW WE BUILD BUSINESS
AROUND TECHNOLOGY AND HOW YOU
CODE.
Simon Wardley

19. more Scalable
(and scales faster!)

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

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

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

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

24. idea production
greater Velocity from idea to product

25. minimise Undifferentiated
heavy-lifting

26. Less ops responsibility on
your shoulders

27. https://www.youtube.com/watch?v=pptsgV4bKv8

29. http://bit.ly/2Dpidje

30. events are an enabler for
COMPOSABILITY

31. AWS LAMBDA
is the...

33. PATTERNS

34. WARNING!!

35. A DESIGN PATTERN IS NOT...
A RECIPE FOR SUCCESS

36. Pattern
/pat(ə)n/
A pattern is the repeated or
regular way in which something
happens or is done.

37. UNDERSTAND YOUR PROBLEMS
AND CONSTRAINTS OVER
FOLLOWING A PATTERN.
me

38. http://bit.ly/2Goq5mY

39. I’m not trying to sell you a “magic” elixir!

40. there are no silver bullets

41. Pattern
/pat(ə)n/
A pattern is the repeated or
regular way in which something
happens or is done.

42. Yan Cui
http://theburningmonk.com
@theburningmonk
Principal Engineer @

43. “Netflix for sports”
offices in London, Leeds, Katowice and Tokyo

47. available in Austria, Switzerland,
Germany, Japan and Canada

48. available on 30+ platforms

49. ~500,000 concurrent viewers

50. “Netflix for sports”
offices in London, Leeds, Katowice and Tokyo
We’re hiring! Visit
engineering.dazn.com to
learn more.
follow @DAZN_ngnrs for
updates about the
engineering team.

51. AWS user since 2009

52. http://bit.ly/yubl-serverless

53. http://bit.ly/2Cdsai5

54. CRON

55. AWS LambdaCloudWatch Events

56. CloudWatch Events

59. OPS
AUTOMATION

60. AWS Lambda CloudWatch Logs

61. CloudWatch Logs

62. AWS Lambda CloudWatch Logs AWS Lambda

63. CloudWatch Logs

64. AWS Lambda CloudWatch Logs
CloudTrail

65. CloudWatch Events

68. AWS Lambda CloudWatch Logs
CloudWatch Events
CloudTrail
AWS Lambda

69. AWS Lambda CloudWatch Logs
CloudWatch Events
CloudTrail
AWS Lambda
AWS Lambda

70. AWS Lambda CloudWatch Logs
CloudWatch Events
CloudTrail
AWS Lambda
AWS Lambda

71. auto-update CloudWatch retention policy
auto-create alarms for new APIs
auto-create dashboards for new APIs
alert on suspicious console logins
alert on EC2 activities in unused regions
…

72. WEB APPS

73. CloudFront S3
Browser

74. API Gateway AWS Lambda DynamoDBRoute53
CloudFront S3
Browser

75. API Gateway AWS Lambda DynamoDBRoute53
CloudFront S3
Browser
Cognito

76. Federated
Identities
Sync
User Flows
Registration
Verify email/phone
Secure sign-in
Forgotten password
Change password
Sign out
Cognito User
Pools

77. Federated
Identities
Sync
Leading Practices
Secure password handling
with SRP protocol
Encrypt all data server-side
Password policies
Token-based authentication
MFA
Support CAPTCHA
Cognito User
Pools

78. Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
authenticate

79. Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
authenticate token

80. Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
authenticate token
token

81. validate
Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
authenticate token
token

82. validate
Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
authenticate token
token
IAM credential

83. validate
Cognito
Federated Identities
Cognito
User Pools
Facebook TwitterGoogle
…
identity providers
API Gateway S3 DynamoDB SNSIOT Kinesis
authenticate token
token
IAM credential
IAM credential

84. what about Multi-Region support?

85. https://aws.amazon.com/dynamodb/global-tables

86. http://amzn.to/2Bwb5j6

87. API Gateway AWS Lambda
DynamoDB
Route53
CloudFront S3
Browser
API Gateway AWS Lambda
eu-west-1
us-east-1

88. http://bit.ly/2FGKsuA

89. DATA LAKES

90. S3 Buckets

91. S3 Buckets
IAM

92. S3 Buckets
KMSIAM

93. S3 Buckets
KMS MacieIAM

94. S3 BucketsKinesis Streams Kinesis Firehose
KMS MacieIAM

95. S3 BucketsKinesis Streams
AWS Lambda
KMS MacieIAM
Kinesis Firehose

96. S3 BucketsKinesis Streams
AWS Lambda
KMS MacieIAM
AWS Lambda
Kinesis Firehose

97. S3 BucketsKinesis Streams
AWS Lambda AWS Lambda
KMS MacieIAM
AWS Lambda
Kinesis Firehose

98. S3 BucketsKinesis Streams
AWS Lambda AWS Lambda
KMS MacieIAM
AWS Lambda
DynamoDB
ElasticSearch
Kinesis Firehose

99. S3 BucketsKinesis Streams
AWS Lambda AWS Lambda
KMS MacieIAM
AWS Lambda Google BigQuery
Kinesis Firehose

100. S3 BucketsKinesis Streams
AWS Lambda AWS Lambda
Athena QuickSight
KMS MacieIAM
AWS Lambda
Kinesis Firehose

101. S3 BucketsKinesis Streams
AWS Lambda AWS Lambda
Athena QuickSight
KMS MacieIAM
AWS Lambda
Kinesis Firehose

102. EVENT
DRIVEN

103. http://bit.ly/2Dpidje

104. Kinesis

105. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B

106. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B

107. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B
AWS Lambda
AWS Lambda
AWS Lambda

108. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B
AWS Lambda
AWS Lambda
AWS Lambda DynamoDBIOT

109. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B
AWS Lambda
AWS Lambda
AWS Lambda DynamoDBIOT

110. Kinesis
API Gateway AWS Lambda API GatewayAWS Lambda
service-A service-B
AWS Lambda
AWS Lambda
AWS Lambda DynamoDBIOT
AWS Lambda AWS Lambda

111. build loosely-coupled system
through events

112. service A service B
service C service D
bounded context
bounded context

113. service A service B
service C service D
bounded context
bounded context

114. service A service B
service C service D

116. service A service B
service C service D

117. service A service B
service C service D

119. service A service B
service C service Dbackward-compatible?

121. bounded context
DON’T use events to
orchestrate workflows
within the same
bounded context

122. bounded context
adds unnecessary
complexity to logging,
tracing, and end-to-end
reporting

123. bounded context
the workflow doesn’t exist
as a standalone concept,
but as the sum of a series
of loosely connected parts

124. Step Functions
use Step Functions instead

125. Step Functions
don’t forget to emit events
from the workflow

126. Step Functions
so others can react to state
changes that happened as
part of the workflow

127. DECOUPLED
INVOCATION

128. Decoupled Invocation
How can a service handle normal
request loads, peak request loads,
and a continuous period of high
load without failing?

129. business logic requires expensive processing

130. API Gateway
max integration timeout is 29 seconds
http://amzn.to/2BwW5Bx

131. downstream systems not as scalable

133. decouple reply from the initial request

134. APIClient
POST /do_something

135. workerAPIClient
POST /do_something
202 /result_location
do work

136. workerAPIClient
POST /do_something
202 /result_location
GET /result_location
202 /result_location
do work

137. workerAPIClient
POST /do_something
202 /result_location
GET /result_location
202 /result_location
do work
work done

138. workerAPIClient
POST /do_something
202 /result_location
GET /result_location
202 /result_location
do work
work done
GET /result_location
200 OK

139. amortises spikes in load

141. allows fast response back to caller whilst
promises to finish work later

143. allows flexible retry strategies by removing the
urgency of having to reply to caller right away

144. DynamoDB
API Gateway
POST
task id created at result
xxx xxx <null>
xxx xxx <null>
… … …
task results
not ready
PutItem

145. DynamoDB
API Gateway
POST
task id created at result
xxx xxx <null>
xxx xxx <null>
… … …
task results
not ready
SQS

146. DynamoDB
API Gateway
202
task id created at result
xxx xxx <null>
xxx xxx <null>
… … …
task results
not ready
SQS

147. use “created at” timestamp to timeout
polling requests and avoid infinite retry

148. DynamoDBAPI Gateway
GET
task id created at result
xxx xxx <null>
xxx xxx <null>
… … …
task results
not ready
SQS

149. DynamoDBAPI Gateway
202
task id created at result
xxx xxx <null>
xxx xxx <null>
… … …
task results
not ready
SQS

150. DynamoDB
task id created at result
xxx { … }
xxx <null>
… …
task results
done
UpdateItem
xxx
xxx
…
SQS

151. DynamoDBAPI Gateway
GET
task id created at result
xxx xxx { … }
xxx xxx <null>
… … …
task results
done

152. DynamoDBAPI Gateway
200 { … }

153. also consider using Kinesis Streams or
DynamoDB Streams as queue

154. but SNS is a poor choice
(invocation-per-message means no amortisation)

155. PUB-SUB

156. msg broker
subscriber
subscriber
subscriber
subscriber
…

157. one message, many consumers

158. good for decoupling data processing

159. independent failures
partial failures are easier to manage

160. SNS, Kinesis Streams, DynamoDB Streams, etc…

161. SNS

162. 2 retries then DLQ
SNS

163. 2 retries then DLQ
invocation per msg
SNS

164. 2 retries then DLQ
invocation per msg
might run into
throttling limits
consider impact on
downstream
SNS

165. suffers from temporal issues

166. msg/s
time
max throughput
erred and retried

167. msg/s
time
max throughput
erred and retried

168. msg/s
time
max throughput
downstream outage

169. Kinesis

170. retried until success
Kinesis

171. retried until success
invocation per shard
Kinesis

172. better handling of temporal issues

173. msg/s
time
processed
max throughput amortised
received

174. msg/s
time
max throughput
downstream outage
processed
received

175. DynamoDB
Streams
DynamoDB

176. Kinesis Streams or DynamoDB Streams?

177. what is your source of truth?

178. limited to events from one table

179. records describe DynamoDB events,
not events from your domain

180.