FaaS or not to FaaS: Visible & invisible benefits of the Serverless paradigm
summary
Compares full AWS serverless costs and tradeoffs: Lambda often makes up less than 1% of bill while API Gateway $3.5 per M requests and CloudWatch logs, DynamoDB on‑demand and Step Functions ($25 per 25M transitions) drive costs; concurrency limits are regionally 500–3,000, max Lambda runtime 15 minutes and API Gateway timeout 29s; Java suffers cold starts for Java and provisioned concurrency reduces them but costs extra; recommends event-driven use, idempotent code, and measuring TCO.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:40Value proposition of Serverless
- 7:15Decision checklist
- 8:00Application life cycle
- 9:10Stack ownership
- 10:40The stranger pattern
- 13:05Understanding your workloads
- 15:55Questions to ask yourself
- 19:05Programming model
- 21:00Platform limitations
- 25:55Costs
- 29:05Organizational environment
- 34:33Best practices
- 37:48Platform tooling maturity
related talks
51mFaaS or not to FaaS? Visible and invisible benefits of the Serverless paradigma
54mFaaS or not to FaaS — Visible and Invisible Advantages of the Serverless Paradigm
01h 00mServerless - reality or BS - notes from the trenches
58mServerless: Five Key Things you need to Know
58mServerless Under the Hood
42mServerless Tales from the Trenches
36mTransforming SaaS with Serverless Architectures
05m#Serverless + #Devops = BFF