You should be building Serverless Microservices
summary
Argues that replacing VMs and containers with managed cloud services cuts ops and speeds development, and demonstrates a working CRUD "kittens" API deployed with the Serverless framework using AWS Lambda, API Gateway and DynamoDB, plus static site on S3/CloudFront. Shows deploy via "serverless deploy" which creates CloudFormation, IAM roles and endpoints; API Gateway handles ~10,000 req/s, Lambda default concurrency ~1,000 (can be raised), API cost ~$3.50 per million requests — deployment works end to end.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:16What is service
- 4:06Problems
- 7:16New reality
- 11:40What are Microservices
- 14:02What is a monolithic application
- 18:02Microservices application breakdown
- 22:00Microservices advantages
- 23:36Deployment
- 26:43Build it you run it
- 28:14Service Managed Services
- 30:10Paper Usage Models
- 31:02Microservices Architecture
- 32:03Lambda
- 33:37Lambda Layers
- 36:35No idle running costs
- 39:35Architecture
- 40:29AWS redundancy
- 41:23Other cloud vendors
- 42:33Serverless Service Framework
- 44:20Demo
- 50:16Summary
related talks
28mServerless - the way microservices should be
54mServerless Architectures: no servers allowed!
49mBuilding Scalable APIs Using Serverless
25mHow Serverless Is Changing the World for Developers
04mServerless applications, Microservices, AWS
41mYou Don’t Want to Build a Serverless Monolith
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
20mWhy Serverless Architecture is Changing Software Development