Downloaded 73 times
![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](https://image.slidesharecdn.com/awslambdafromthetrenches-170329220854/75/AWS-Lambda-from-the-trenches-79-2048.jpg)
![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](https://crownmelresort.com/image.slidesharecdn.com/awslambdafromthetrenches-170329220854/75/AWS-Lambda-from-the-trenches-79-2048.jpg)
Uploaded byYan Cui
AWS Lambda from the trenches
The document provides insights into the complexities and best practices for deploying applications using AWS Lambda, emphasizing the importance of independent deployments, cost-minimization, and reduced operational effort. It discusses various testing levels, CI/CD pipeline configurations, monitoring, and logging strategies to ensure effective production readiness. Additionally, it highlights the necessity of managing resources efficiently, understanding cold starts, and handling function failures in serverless architectures.
More Related Content
![[AWS Dev Day] 실습워크샵 | Amazon EKS 핸즈온 워크샵](https://cdn.slidesharecdn.com/ss_thumbnails/awsdevdayseoul2019-amazonekshands-onworkshopv0-190930092336-thumbnail.jpg?width=640&height=640&fit=bounds)
![[AWS Dev Day] 앱 현대화 | AWS Fargate를 사용한 서버리스 컨테이너 활용 하기 - 삼성전자 개발자 포털 사례 - 정영준...](https://cdn.slidesharecdn.com/ss_thumbnails/appmodernizationawsfargate-190930044252-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to AWS Lambda from the trenches
AWS Lambda from the trenches
- 1. from the TRENCHESTRENCHES what youshould know before you go to production AWS LAMBDAAWS LAMBDA
- 2.
- 7. AWS user since2009
- 10.
- 11. hidden complexities anddependencies 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
- 12. - Dan North “leadtime to someone saying thank you is the only reputation metric that matters.”
- 14. “what would good looklike for us?”
- 15. be small be fast havezero downtime have no lock-step DEPLOYMENTS SHOULD...
- 16. FEATURES SHOULD... be deployableindependently be loosely-coupled
- 17. WE WANT TO... minimisecost for unused resources minimise ops effort reduce tech mess deliver visible improvements faster
- 18.
- 19. 170 Lambda functionsin prod 1.2 GB deployment packages in prod 95% cost saving vs EC2 15x no. of prod releases per month
- 20.
- 21. 1st function inprod! time is a good fit
- 22. ? time is a goodfit 1st function in prod!
- 23.
- 24. 170 functions WOOF! ? ? time isa good fit 1st function in prod!
- 25.
- 26.
- 27.
- 28. Legacy Monolith AmazonKinesis Amazon Lambda Amazon CloudSearch
- 29. Legacy Monolith AmazonKinesis Amazon Lambda Amazon CloudSearchAmazon API Gateway Amazon Lambda
- 30.
- 31. Legacy Monolith AmazonKinesis Amazon Lambda Google BigQuery
- 32. Legacy Monolith AmazonKinesis Amazon Lambda Google BigQuery 1 developer, 2 days design production (his 1st serverless project)
- 33. Legacy Monolith AmazonKinesis Amazon Lambda Google BigQuery “nothing ever got done this fast at Skype!” - Chris Twamley
- 34. - Dan North “leadtime to someone saying thank you is the only reputation metric that matters.”
- 35.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59. Level of Testing 1.Unit doour objects do the right thing? are they easy to work with?
- 61. Level of Testing 1.Unit 2.Integration doesour code work against code we can’t change?
- 62.
- 63. handler test by invoking thehandler
- 64. Level of Testing 1.Unit 2.Integration 3.Acceptance doesthe whole system work?
- 65.
- 66. “…We find thattests 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
- 67. “…The second riskis 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
- 68. Don’t Mock TypesYou Can’t Change Services
- 70. “…Wherever possible, anacceptance 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
- 71. Legacy Monolith AmazonKinesis Amazon Lambda Amazon CloudSearchAmazon API Gateway Amazon Lambda
- 72. Legacy Monolith AmazonKinesis Amazon Lambda Amazon CloudSearchAmazon API Gateway Amazon Lambda Test Input
- 73. Legacy Monolith AmazonKinesis Amazon Lambda Amazon CloudSearchAmazon API Gateway Amazon Lambda Test Input Validate
- 74. CI + CDPIPELINE
- 75. “the earlier youconsider CI + CD, the more time you save in the long run” - me
- 76. “…We prefer tohave 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
- 77. “deployment scripts that onlylive on the CI box is a disaster waiting to happen” - me
- 78. Jenkins build configdeploys and tests unit + integration tests deploy acceptance tests
- 79. 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
- 80. build.sh allows repeatablebuilds on both local & CI
- 82.
- 83.
- 85. 2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT isoff air, what do I do now?
- 86. 2016-07-12T12:24:37.571Z 994f18f9-482b-11e6-8668-53e4eab441ae GOT isoff air, what do I do now? UTC Timestamp API Gateway Request Id your log message
- 87.
- 88.
- 89.
- 90. CENTRALISE LOGS MAKE THEMEASILY SEARCHABLE
- 91. + + the elkstack
- 92.
- 93. CloudWatch Logs AWSLambda ELK stack
- 94.
- 96.
- 97.
- 99. “my followers didn’t receivemy new post!” - a user
- 100.
- 101. correlation IDs* * eg.request-id, user-id, yubl-id, etc.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108. traces do notspan over API Gateway
- 109. useful, but hamperedby current limitations
- 110.
- 111.
- 112. “where do Iinstall monitoring agents?”
- 113.
- 114. • invocation Count •error Count • latency • throttling • granular to the minute • support custom metrics
- 115. • same metricsas CW • better dashboard • support custom metrics https://www.datadoghq.com/blog/monitoring-lambda-functions-datadog/
- 117. “how do Ibatch up and send logs in the background?”
- 118.
- 119. console.log(“hydrating yubls fromdb…”); 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
- 120. CloudWatch Logs AWSLambda ELK stack logs metrics CloudWatch
- 121.
- 122.
- 123.
- 124.
- 125.
- 127. “you really don'twant your monitoring system to fail at the same time as the system it monitors” - me
- 128.
- 129. easily and quicklypropagate config changes
- 131.
- 132.
- 136.
- 137.
- 139.
- 140. sensitive data shouldbe encrypted in-flight, and at rest (credentials, connection string, etc.)
- 141.
- 142.
- 143. EC2 Parameter Store HTTPS role-basedaccess encrypted in-flight
- 144.
- 145.
- 146. HTTPS role-based access EC2 ParameterStore encrypted in-flight
- 147.
- 148.
- 149.
- 150. max 75 GBtotal deployment package size* * limit is per AWS region
- 151.
- 152.
- 153.
- 154.
- 155. install Serverless frameworkas dev dependency at project level dev dependencies are excluded since 1.16.0
- 156.
- 157.
- 158.
- 159. Amazon X-Ray 1st invocation 2ndinvocation cold start
- 160.
- 161.
- 162.
- 163.
- 164.
- 165.
- 166.
- 167. what about typesafety?
- 169. complexity ceiling ofa Node.js app complexity
- 170. complexity ceiling ofa Node.js app complexity referential transparency immutability as default type inference option types union types …
- 171. for managing complexity complexityceiling of a Node.js app complexity referential transparency immutability as default type inference option types union types …
- 172. complexity ceiling ofa Node.js app complexity complexity ceiling of a Node.js Lambda function
- 173. if you canlimit the complexity of your solution, maybe you won’t need the tools for managing that complexity. me
- 174.
- 175.
- 176.
- 177. CloudWatch Event AWSLambda
- 178. CloudWatch Event AWSLambda ping ping ping ping
- 179. CloudWatch Event AWSLambda ping ping ping ping
- 180. CloudWatch Event AWSLambda ping ping ping ping HEALTH CHECKS?
- 181. max 5 minsexecution time
- 182.
- 183.
- 184. “AWS Lambda pollsyour stream and invokes your Lambda function. Therefore, if a Lambda function fails, AWS Lambda attempts to process the erring batch of records until the time the data expires…” http://docs.aws.amazon.com/lambda/latest/dg/retries-on-errors.html
- 185. should function failon partial/any failures?
- 186. SNS Kinesis SQS after 3 attempts shareprocessing logic events are processed in chronological order failed events are retried out of sequence
- 187.
- 188.
- 189.
- 190. “Each shard cansupport up to 5 transactions per second for reads, up to a maximum total data read rate of 2 MB per second.” http://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html
- 191. “If your streamhas 100 active shards, there will be 100 Lambda functions running concurrently. Then, each Lambda function processes events on a shard in the order that they arrive.” http://docs.aws.amazon.com/lambda/latest/dg/concurrent-executions.html
- 192. when no. ofprocessors goes up…
- 193. ReadProvisionedThroughputExceeded can have toomany Kinesis read operations…
- 194. ReadRecords.IteratorAge unpredictable spikes inread ‘latency’…
- 195.
- 196.
- 197.
- 198. for subsystems thatdon’t have to be realtime, or are task- based (ie. order doesn’t matter), consider other triggers such as S3 or SNS.me
- 199.
- 200. sign up here:http://bit.ly/2xCwJEe