Page 1
from the
TRENCHESTRENCHES
what you should know before you go to production
AWS LAMBDAAWS LAMBDA
Page 3
hi, I’m Yan CuiAWS user since 2009
Page 11
hidden complexities and dependencies
low utilisation to leave room for traffic spikes
EC2 scaling is slow, so scale earlier
lots of cost for unused resources
up to 30 mins for deployment
deployment required downtime
Page 12
- Dan North
“lead time to someone saying thank you is the only reputation
metric that matters.”
Page 14
“what would good
look like for us?”
Page 15
be small be fast
have zero downtime have no lock-step
DEPLOYMENTS SHOULD...
Page 16
FEATURES SHOULD...be deployable independently
be loosely-coupled
Page 17
WE WANT TO...minimise cost for unused resources
minimise ops effort reduce tech mess
deliver visible improvements faster
Page 19
170 Lambda functions in prod
1.2 GB deployment packages in prod
95% cost saving vs EC2
15x no. of prod releases per month
Page 20
timeis a good fit
Page 21
1st function in prod!time
is a good fit
Page 22
?
timeis a good fit
1st function in prod!
Page 23
ALERTING
CI / CD
TESTING
LOGGING
MONITORING
Page 24
Practices ToolsPrinciples
what is good? how to make it good? with what?
Page 25
Principles outlast Tools
Page 26
170 functions
WOOF!
? ?
timeis a good fit
1st function in prod!
Page 27
SECURITY
DISTRIBUTEDTRACING
CONFIGMANAGEMENT
Page 28
evolving the PLATFORM
Page 30
Legacy Monolith Amazon Kinesis Amazon Lambda
Amazon CloudSearch
Page 31
Legacy Monolith Amazon Kinesis Amazon Lambda
Amazon CloudSearchAmazon API Gateway Amazon Lambda
Page 32
new analytics pipeline
Page 33
Legacy Monolith Amazon Kinesis Amazon Lambda
Google BigQuery
Page 34
Legacy Monolith Amazon Kinesis Amazon Lambda
Google BigQuery
1 developer, 2 daysdesign production
(his 1st serverless project)
Page 35
Legacy Monolith Amazon Kinesis Amazon Lambda
Google BigQuery“nothing ever got done
this fast at Skype!”
- Chris Twamley
Page 36
- Dan North
“lead time to someone saying thank you is the only reputation
metric that matters.”
Page 37
Rebuiltwith Lambda
Page 44
Rebuiltwith Lambda
Page 47
grapheneDB
BigQuery
Page 48
grapheneDB
BigQuery
Page 49
grapheneDB
BigQuery
Page 50
getting PRODUCTION READY
Page 51
CHOOSE A
FRAMEWORK
DEPLOYMENT
Page 52
http://serverless.com
Page 53
https://github.com/awslabs/serverless-application-model
Page 55
https://apex.github.io/up
Page 56
https://github.com/claudiajs/claudia
Page 57
https://github.com/Miserlou/Zappa
Page 58
http://gosparta.io/
Page 61
Level of Testing
1.Unitdo our objects do the right thing?are they easy to work with?
Page 63
Level of Testing
1.Unit2.Integrationdoes our code work against code we can’t change?
Page 65
handler
test by invoking the handler
Page 66
Level of Testing
1.Unit2.Integration3.Acceptancedoes the whole system work?
Page 67
Level of Testing
unit
integration
acceptance
feedb
ack
confidence
Page 68
“…We find that tests that mock external libraries often need to be complex to get the code into the right state for the functionality we need to exercise.
The mess in such tests is telling us that the design isn’t right but, instead of fixing the problem by improving the code, we have to carry the extra complexity in both code and test…”
Don’t Mock Types You Can’t Change
Page 69
“…The second risk is that we have to be sure that the behaviour we stub or mock matches what the external library will actually do…
Even if we get it right once, we have to make sure that the tests remain valid when we upgrade the libraries…”
Don’t Mock Types You Can’t Change
Page 70
Don’t Mock Types You Can’t ChangeServices
Page 71
Paul Johnston
The serverless approach to testing is different and may
actually be easier.
http://bit.ly/2t5viwK
Page 72
LambdaAPI Gateway DynamoDB
Page 73
LambdaAPI Gateway DynamoDB
Unit Tests
Page 74
LambdaAPI Gateway DynamoDB
Unit Tests
Mock/Stub
Page 75
is our request correct?
is the request mapping set up correctly?is the API resources
configured correctly?
are we assuming the correct schema?
LambdaAPI Gateway DynamoDB
is Lambda proxy configured correctly?
is IAM policy set up correctly?
is the table created?
what unit tests will not tell you…
Page 77
most Lambda functions are simple have single purpose, the risk of
shipping broken software has largely shifted to how they integrate with
external services
observation
Page 79
But it slows down my feedback loop…
IT’S NOT ABOUT YOU!
Page 80
…if a service can’t provide you with a relatively easy
way to test the interface in reality, then you should
consider using another one.
Paul Johnston
Page 81
“…Wherever possible, an acceptance test should exercise the system end-to-end without directly calling its internal code.
An end-to-end test interacts with the system only from the outside: through its interface…”
Testing End-to-End
Page 82
Legacy Monolith Amazon Kinesis Amazon Lambda
Amazon CloudSearchAmazon API Gateway Amazon Lambda
Page 83
Legacy Monolith Amazon Kinesis Amazon Lambda
Amazon CloudSearchAmazon API Gateway Amazon Lambda
Test Input
Page 84
Legacy Monolith Amazon Kinesis Amazon Lambda
Amazon CloudSearchAmazon API Gateway Amazon Lambda
Test Input
Validate
Page 85
integration tests exercise system’s Integration with its
external dependencies
Page 86
acceptance tests exercise system End-to-End from
the outside
Page 87
integration tests differ from acceptance tests only in HOW the
Lambda functions are invoked
observation
Page 92
“the earlier you consider CI + CD, the more time you save in the long run”
- me
Page 93
“…We prefer to have the end-to-end tests exercise both the system and the process by which it’s built and deployed…
This sounds like a lot of effort (it is), but has to be done anyway repeatedly during the software’s lifetime…”
Testing End-to-End
Page 94
“deployment scripts that only live on the CI
box is a disaster waiting to happen”
- me
Page 95
Jenkins build config deploys and tests
unit + integration tests
deploy
acceptance tests
Page 96
if [ "$1" = "deploy" ] && [ $# -eq 4 ]; then STAGE=$2 REGION=$3 PROFILE=$4
npm install AWS_PROFILE=$PROFILE 'node_modules/.bin/sls' deploy -s $STAGE -r $REGION elif [ "$1" = "int-test" ] && [ $# -eq 4 ]; then STAGE=$2 REGION=$3 PROFILE=$4
npm install AWS_PROFILE=$PROFILE npm run int-$STAGE elif [ "$1" = "acceptance-test" ] && [ $# -eq 4 ]; then STAGE=$2 REGION=$3 PROFILE=$4
npm install AWS_PROFILE=$PROFILE npm run acceptance-$STAGE else usage exit 1 fi
Page 97
build.sh allows repeatable builds on both local & CI
Page 102
2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT is off air, what do I do now?
Page 103
2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT is off air, what do I do now?
UTC Timestamp API Gateway Request Id
your log message
Page 104
function name
date
function version
Page 105
me
Logs are not easily searchable in CloudWatch Logs.
Page 108
CENTRALISE LOGS
MAKE THEM EASILYSEARCHABLE
Page 109
+ +the elk stack
Page 111
CloudWatch Logs AWS Lambda ELK stack
Page 112
CloudWatch Events
Page 114
http://bit.ly/2f3zxQG
Page 115
DISTRIBUTED TRACING
Page 117
“my followers didn’t receive my new post!”
- a user
Page 118
where could the problem be?
Page 119
correlation IDs*
* eg. request-id, user-id, yubl-id, etc.
Page 120
ROLL YOUR OWNCLIENTS
Page 121
kinesis client
http client
sns client
Page 122
http://bit.ly/2k93hAj
Page 123
ROLL YOUR OWNCLIENTS
X-RAY
Page 126
traces do not span over API Gateway
Page 127
http://bit.ly/2s9yxmA
Page 128
MONITORING + ALERTING
Page 129
“where do I install monitoring agents?”
Page 131
• invocation Count• error Count• latency• throttling• granular to the minute• support custom metrics
Page 132
• same metrics as CW• better dashboard• support custom metrics
https://www.datadoghq.com/blog/monitoring-lambda-functions-datadog/
Page 138
my codeinternet internet
press button something happens
Page 139
“how do I batch up and send logs in the
background?”
Page 140
you can’t (kinda)
Page 141
console.log(“hydrating yubls from db…”);
console.log(“fetching user info from user-api”);
console.log(“MONITORING|1489795335|27.4|latency|user-api-latency”);
console.log(“MONITORING|1489795335|8|count|yubls-served”);
timestamp metric value
metric type
metric namemetrics
logs
Page 142
CloudWatch Logs AWS Lambda
ELK stacklogs
metrics
CloudWatch
Page 143
http://bit.ly/2gGredx
Page 145
DASHBOARDS
SET ALARMS
Page 146
DASHBOARDS
SET ALARMS
TRACK APP-LEVELMETRICS
Page 147
Not Only CloudWatch
Page 149
“you really don't want your monitoring
system to fail at the same time as the
system it monitors” - me
Page 150
CONFIG MANAGEMENT
Page 151
easily and quickly propagate config changes
Page 153
me
Environment variables make it hard to share configurations
across functions.
Page 154
me
Environment variables make it hard to implement fine-grained
access to sensitive info.
Page 155
CENTRALISEDCONFIG SERVICE
Page 156
config servicegoes here
Page 160
SSM Parameter
Store
Page 161
sensitive data should be encrypted in-flight, and at rest
(credentials, connection string, etc.)
Page 162
role-based access
Page 163
SSM Parameter Store
HTTPS
role-based access
encrypted in-flight
Page 164
SSM Parameter Store
encrypt
role-based access
Page 165
SSM Parameter Store
encrypted at-rest
Page 166
HTTPS
role-based access
SSM Parameter Store
encrypted in-flight
Page 167
CENTRALISEDCONFIG SERVICE
CLIENT LIBRARY
Page 168
fetch & cache at Cold Start
Page 169
invalidate at interval + signal
Page 170
http://bit.ly/2yLUjwd
Page 172
max 75 GB total deployment package size*
* limit is per AWS region
Page 174
Janitor Lambda
http://bit.ly/2xzVu4a
Page 175
disable versionFunctions in
Page 176
install Serverless framework as dev dependency at project level
dev dependencies are excluded since 1.16.0
Page 177
http://bit.ly/2vzBqhC
Page 178
http://amzn.to/2vtUkDU
Page 179
UNDERSTANDCOLDSTARTS
Page 180
Amazon X-Ray1st invocation
2nd invocation
cold start
Page 181
source: http://bit.ly/2oBEbw2
Page 182
http://bit.ly/2rtCCBz
Page 183
C#
http://bit.ly/2rtCCBz
Page 184
Java
http://bit.ly/2rtCCBz
Page 185
NodeJs, Python
http://bit.ly/2rtCCBz
Page 187
CloudWatch Event AWS Lambda
Page 188
CloudWatch Event AWS Lambda
ping
ping
ping
ping
Page 189
CloudWatch Event AWS Lambda
ping
ping
ping
ping
Page 190
CloudWatch Event AWS Lambda
ping
ping
ping
ping
HEALTH CHECKS?
Page 191
AVOID HARDASSUMPTIONS
ABOUT FUNCTIONLIFETIME
Page 192
USE STATE FOR
OPTIMISATION
Page 193
max 5 mins execution time
Page 194
USE RECURSIONFOR LONG
RUNNING TASKS
Page 195
@theburningmonktheburningmonk.comgithub.com/theburningmonk
Page 196
@theburningmonktheburningmonk.comgithub.com/theburningmonk
http://bit.ly/2yQZj1H
all my blog posts on Lambda