Serverless for frontend developers
summary
Migrates frontend preprocessing into small serverless functions so builds an on-demand backend that scales automatically and drops provisioning costs dramatically. Uses S3 + Lambda style storage and functions, deploys with a single command via Serverless/CLI or similar, and supports server-side rendering from those functions. A reported production footprint handles about 200,000 requests per hour, pays per invocation instead of reserved servers, and drastically reduces wasted capacity while keeping deployment simple.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:42Who is Aleksandar
- 1:23What about to talk
- 1:47What is Stability
- 3:50Classical servers
- 4:19The problem
- 5:07Front developers
- 5:52Old architecture
- 6:25New architecture
- 6:37Cost reduction
- 7:04Service level value
- 7:16What does it matter to me
- 7:33String
- 7:45Images
- 8:14Sensor Versatility
- 9:23Functions
- 9:55Example
- 12:03Service Functions
- 12:23Frontend Engineers
- 12:57Serviceable modifications
- 15:24Deployment
- 16:16Cost
- 17:58Serverside rendering
- 18:23HTML code
- 19:24Summary
- 21:15Learn more
related talks
51mServerless - a backend thing that gives superpowers to frontend developers
44mServerless: Giving superpowers to frontend developers
14mServerless for frontend engineers, in 10 minutes
54mServerless Architectures: no servers allowed!
32mServerless can do that?!
39mServerless in production, an experience report
20mWhy Serverless Architecture is Changing Software Development
28mServerless - the way microservices should be