Download to read offline
Uploaded byYan Cui
Architectural changes with serverless
The document discusses the concept and benefits of serverless architecture, emphasizing how it enables developers to avoid server management, scale resources automatically, and reduce costs. It highlights various serverless services like AWS Lambda and the importance of event-driven applications for composability. Additionally, it advises leveraging managed services to enhance application development velocity and reduce operational responsibilities.
More Related Content
Similar to Architectural changes with serverless
Architectural changes with serverless
- 1.
- 2.
- 3. “Netflix for sports” officesin London, Leeds, Katowice and Tokyo
- 4. “Netflix for sports” officesin London, Leeds, Katowice and Tokyo We’re hiring! Visit engineering.dazn.com to learn more. follow @DAZN_ngnrs for updates about the engineering team.
- 5.
- 11.
- 13. Gojko Adzic It isserverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 14. 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
- 15. “Function-as-a-Service” AWS Lambda Azure Functions GoogleCloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 16.
- 17. AWS Lambda API GatewayIOT SNS Kinesis CloudWatch
- 18.
- 19.
- 20.
- 21. SERVERLESS WILL FUNDAMENTALLY CHANGEHOW WE BUILD BUSINESS AROUND TECHNOLOGY AND HOW YOU CODE. Simon Wardley
- 22. more Scalable (and scalesfaster!)
- 23. Cheaper (don’t pay foridle servers)
- 24. Resilience (built-in redundancy andmulti-AZ)
- 25. 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
- 26. 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
- 27. idea production greater Velocityfrom idea to product
- 28.
- 29. Less ops responsibilityon your shoulders
- 31.
- 32. mm.. I noticesome trends here
- 33.
- 34.
- 35.
- 36. events are anenabler for COMPOSABILITY
- 37.
- 38.
- 39. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B
- 40. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B
- 41. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda
- 42. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT
- 43. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT
- 44. Kinesis API Gateway AWSLambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT AWS Lambda AWS Lambda
- 45.
- 46. service A serviceB service C service D bounded context bounded context
- 47. service A serviceB service C service D bounded context bounded context
- 48. service A serviceB service C service D
- 50. service A serviceB service C service D
- 51. service A serviceB service C service D
- 53. service A serviceB service C service Dbackward-compatible?
- 55. bounded context DON’T useevents to orchestrate workflows within the same bounded context
- 56. bounded context adds unnecessary complexityto logging, tracing, and end-to-end reporting
- 57. bounded context the workflowdoesn’t exist as a standalone concept, but as the sum of a series of loosely connected parts
- 58. Step Functions use StepFunctions instead
- 59. Step Functions don’t forgetto emit events from the workflow
- 60. Step Functions so otherscan react to state changes that happened as part of the workflow
- 61.
- 62.
- 63. “we want towork with services, not servers”
- 65. “in the midstof all these new problems, do you wanna waste time running your own infrastructure right now?” - Austen Collins, CEO Serverless Inc
- 67. “use as manymanaged services as you can” - Ben Kehoe, Cloud Scientist iRobot
- 68.
- 69. “I want tobuild a data pipeline”
- 70.
- 71.
- 72.
- 73.
- 74. S3 BucketsKinesis StreamsKinesis Firehose KMS MacieIAM
- 75. S3 BucketsKinesis Streams AWSLambda KMS MacieIAM Kinesis Firehose
- 76. S3 BucketsKinesis Streams AWSLambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 77. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 78. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda DynamoDB ElasticSearch Kinesis Firehose
- 79. S3 BucketsKinesis Streams AWSLambda AWS Lambda KMS MacieIAM AWS Lambda Google BigQuery Kinesis Firehose
- 80. S3 BucketsKinesis Streams AWSLambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 81. S3 BucketsKinesis Streams AWSLambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 82.
- 83.
- 84.
- 85.
- 86. functions are ephemeralby design
- 87.
- 88. secure sensitive databoth at rest and in-transit
- 89.
- 90.
- 91.
- 92.
- 93.
- 94. principle of LeastPrivilege
- 95. keep functions single-purposed &apply per function policies
- 97.
- 98. 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
- 99. idea production greater Velocityfrom idea to product
- 100.
- 101.
- 102. “use as manymanaged services as you can” - Ben Kehoe, Cloud Scientist iRobot
- 103.
- 104.