Serverless - a backend thing that gives superpowers to frontend developers
summary
Claims that front-end teams get “superpowers” by moving preprocessing and APIs to serverless backed by concrete tools and numbers: CodePen migrates Sass/TypeScript processors to AWS Lambda and handles ~200k requests/hour with bursts to 5,000 parallel functions, cost example 20–50M requests ≈ $1,180/month; a Slack vacation bot runs on S3, API Gateway, Lambda, DynamoDB and Stripe and costs ~$0.14/month; demos use Claudia.js and deployment via Amplify, and these systems are shown working in production.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:13Why serverless matters
- 5:12What is serverless
- 10:29Key advantages
- 13:20Superpowers for frontend
- 14:05Codrops case study
- 19:31Hackathon serverless app
- 23:27Getting started
- 28:06Serverless tools
- 32:04Live demo API
- 37:45Summary
- 39:03Q&A
related talks
44mServerless: Giving superpowers to frontend developers
27mServerless for frontend developers
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
32mServerless can do that?!
14mServerless for frontend engineers, in 10 minutes
28mServerless - the way microservices should be
20mWhy Serverless Architecture is Changing Software Development
01h 00mServerless - reality or BS - notes from the trenches
