Why Serverless Architecture is Changing Software Development
summary
Argues serverless runs code on demand with AWS Lambda and pays only for execution, not idle hours, and the first million requests per month can be free. Shows concrete stacks: Node functions zipped with npm deps, triggered by S3 uploads or DynamoDB changes to resize images or send welcome emails, and deployed with the Serverless Framework. Gives measurable wins: a web-scrape job drops from 8 hours to 4 minutes via concurrent Lambdas; demos include a low-cost MailChimp replica and a working social-network composed of microservices.
AI-written summary · about
chapters (8)
- 0:00History of serverless
- 1:33Why use serverless
- 4:08Core serverless concepts
- 6:16Getting started with Lambda
- 8:27Serverless use cases
- 10:24Deployment and infrastructure
- 14:44Common architectural patterns
- 17:33Advanced scaling and closing
related talks
25mHow Serverless Is Changing the World for Developers
28mServerless - the way microservices should be
48mThe future will be Serverless
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
45mThe State Of Serverless
31mA quick intro to AWS Serverless
56m8 1/2 things about serverless (with Node.js)
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
