Download as PDF, PPTX
Uploaded byYan Cui
Serveless design patterns
The document discusses serverless design patterns and the advantages of serverless computing, such as cost efficiency and scalability. It emphasizes the importance of understanding problems and constraints rather than rigidly following design patterns, and highlights various services like AWS Lambda and DynamoDB. Additionally, it explores strategies for managing load, improving resilience, and integrating different AWS services in a serverless architecture.
More Related Content
Similar to Serveless design patterns
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Serveless design patterns
- 1.
- 2.
- 3.
- 9.
- 11. Gojko Adzic It isserverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 12. Serverless means… don’t payfor it if no-one uses it don’t need to worry about scaling don’t need to provision and manage servers
- 13. “Function-as-a-Service” AWS Lambda Azure Functions GoogleCloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 14.
- 15. AWS Lambda API GatewayIOT SNS Kinesis CloudWatch
- 16.
- 17.
- 18.
- 19. SERVERLESS WILL FUNDAMENTALLY CHANGEHOW WE BUILD BUSINESS AROUND TECHNOLOGY AND HOW YOU CODE. Simon Wardley
- 20. more Scalable (and scalesfaster!)
- 21. Cheaper (don’t pay foridle servers)
- 22. Resilience (built-in redundancy andmulti-AZ)
- 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 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
- 25. idea production greater Velocityfrom idea to product
- 26.
- 27. Less ops responsibilityon your shoulders
- 28.
- 30.
- 31. events are anenabler for COMPOSABILITY
- 32.
- 34.
- 35.
- 36. A DESIGN PATTERNIS NOT... A RECIPE FOR SUCCESS
- 37. Pattern /pat(ə)n/ A pattern isthe repeated or regular way in which something happens or is done.
- 38. UNDERSTAND YOUR PROBLEMS ANDCONSTRAINTS OVER FOLLOWING A PATTERN. me
- 39.
- 40. I’m not tryingto sell you a “magic” elixir!
- 41. there are nosilver bullets
- 42. Pattern /pat(ə)n/ A pattern isthe repeated or regular way in which something happens or is done.
- 43.
- 44.
- 45.
- 48.
- 49.
- 50.
- 51. AWS Lambda CloudWatchLogs AWS Lambda
- 52.
- 53. AWS Lambda CloudWatchLogs CloudTrail
- 54.
- 57. AWS Lambda CloudWatchLogs CloudWatch Events CloudTrail AWS Lambda
- 58. AWS Lambda CloudWatchLogs CloudWatch Events CloudTrail AWS Lambda AWS Lambda
- 59. AWS Lambda CloudWatchLogs CloudWatch Events CloudTrail AWS Lambda AWS Lambda
- 60. auto-update CloudWatch retentionpolicy auto-create alarms for new APIs auto-create dashboards for new APIs alert on suspicious console logins alert on EC2 activities in unused regions …
- 61.
- 62.
- 63. API Gateway AWSLambda DynamoDBRoute53 CloudFront S3 Browser
- 64. API Gateway AWSLambda DynamoDBRoute53 CloudFront S3 Browser Cognito
- 65. Federated Identities Sync User Flows Registration Verify email/phone Securesign-in Forgotten password Change password Sign out Cognito User Pools
- 66. Federated Identities Sync Leading Practices Secure passwordhandling with SRP protocol Encrypt all data server-side Password policies Token-based authentication MFA Support CAPTCHA Cognito User Pools
- 67. Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers authenticate
- 68. Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers authenticate token
- 69. Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers authenticate token token
- 70. validate Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers authenticate token token
- 71. validate Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers authenticate token token IAM credential
- 72. validate Cognito Federated Identities Cognito User Pools FacebookTwitterGoogle … identity providers API Gateway S3 DynamoDB SNSIOT Kinesis authenticate token token IAM credential IAM credential
- 73. what about Multi-Regionsupport?
- 74.
- 75.
- 76. API Gateway AWSLambda DynamoDB Route53 CloudFront S3 Browser API Gateway AWS Lambda eu-west-1 us-east-1
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83. S3 BucketsKinesis StreamsKinesis Firehose KMS MacieIAM
- 84. S3 BucketsKinesis Streams AWSLambda KMS MacieIAM Kinesis Firehose
- 85. S3 BucketsKinesis Streams AWSLambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 86. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 87. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda DynamoDB ElasticSearch Kinesis Firehose
- 88. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda Google BigQuery Kinesis Firehose
- 89. S3 BucketsKinesis Streams AWSLambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 90. S3 BucketsKinesis Streams AWSLambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 91.
- 92. Decoupled Invocation How cana service handle normal request loads, peak request loads, and a continuous period of high load without failing?
- 93. business logic requiresexpensive processing
- 94. API Gateway max integrationtimeout is 29 seconds http://amzn.to/2BwW5Bx
- 95. downstream systems notas scalable
- 97. decouple reply fromthe initial request
- 98.
- 99.
- 100. workerAPIClient POST /do_something 202 /result_location GET/result_location 202 /result_location do work
- 101. workerAPIClient POST /do_something 202 /result_location GET/result_location 202 /result_location do work work done
- 102. workerAPIClient POST /do_something 202 /result_location GET/result_location 202 /result_location do work work done GET /result_location 200 OK
- 103.
- 105. allows fast responseback to caller whilst promises to finish work later
- 107. allows flexible retrystrategies by removing the urgency of having to reply to caller right away
- 108. DynamoDB API Gateway POST task idcreated at result xxx xxx <null> xxx xxx <null> … … … task results not ready PutItem
- 109. DynamoDB API Gateway POST task idcreated at result xxx xxx <null> xxx xxx <null> … … … task results not ready SQS
- 110. DynamoDB API Gateway 202 task idcreated at result xxx xxx <null> xxx xxx <null> … … … task results not ready SQS
- 111. use “created at”timestamp to timeout polling requests and avoid infinite retry
- 112. DynamoDBAPI Gateway GET task idcreated at result xxx xxx <null> xxx xxx <null> … … … task results not ready SQS
- 113. DynamoDBAPI Gateway 202 task idcreated at result xxx xxx <null> xxx xxx <null> … … … task results not ready SQS
- 114. DynamoDB task id createdat result xxx { … } xxx <null> … … task results done UpdateItem xxx xxx … SQS
- 115. DynamoDBAPI Gateway GET task idcreated at result xxx xxx { … } xxx xxx <null> … … … task results done
- 116.
- 117. also consider usingKinesis Streams or DynamoDB Streams as queue
- 118. but SNS isa poor choice (invocation-per-message means no amortisation)
- 119.
- 120.
- 121. one message, manyconsumers
- 122. good for decouplingdata processing
- 123. independent failures partial failuresare easier to manage
- 124. SNS, Kinesis Streams,DynamoDB Streams, etc…
- 125.
- 126. 2 retries thenDLQ SNS
- 127. 2 retries thenDLQ invocation per msg SNS
- 128. 2 retries thenDLQ invocation per msg might run into throttling limits consider impact on downstream SNS
- 129. suffers from temporalissues
- 130.
- 131.
- 132.
- 133.
- 134.
- 135. retried until success invocationper shard Kinesis
- 136. better handling oftemporal issues
- 137.
- 138.
- 139.
- 140. Kinesis Streams orDynamoDB Streams?
- 141. what is yoursource of truth?
- 142. limited to eventsfrom one table
- 143. records describe DynamoDBevents, not events from your domain
- 144. auto-scales no. ofshards
- 145. cannot extend dataretention beyond 24 hours
- 146. charged based onno. of requests ($0.02 per 100,000 read request units)
- 148. 1 msg/s fora month, 1KB per msg $0.47 1 x 60s x 60m x 24hr x 30days @ $0.014 per mil + 24hrs x 30days @ $0.015 per hr $10.836 1 x 60s x 60m x 24hr x 30days @ $0.5 per mil $1.296 DynamoDB StreamsSNSKinesis Streams 1 Write Capacity Unit @ $0.47 per unit
- 149. 1k msg/s fora month, 1KB per msg 1k x 60s x 60m x 24hr x 30days @ $0.014 per mil + 24hrs x 30days @ $0.015 per hr $47.088 1k x 60s x 60m x 24hr x 30days @ $0.5 per mil $1296.00 DynamoDB StreamsSNSKinesis Streams $470.00 1k Write Capacity Unit @ $0.47 per unit
- 150. DON’T take theseprojections at face value!
- 151.
- 152. no restriction on destinationtarget SNS
- 153. no restriction on destinationtarget need to handle partial failures & retries SNS
- 154.
- 155. pattern for managingfailures where each action has a compensating action for rollback
- 156.
- 157. Begin transaction Start bookhotel request End book hotel request Start book flight request End book flight request Start book car rental request End book car rental request End transaction
- 158. model actions andcompensating actions as Lambda functions
- 159.
- 160.
- 161. state machine inAWS Step Functions as the coordinator for the saga
- 162.
- 163.
- 167. source code availablehere: https://github.com/theburningmonk/lambda-saga-pattern
- 168.