Serverless for frontend engineers, in 10 minutes
summary
Serverless treats the backend as JavaScript functions as backend that a cloud platform calls on an HTTP request, handling SSL, scaling, and secret storage so engineers avoid VPS and nginx. Examples include calling Stripe or an email API from a function, and platforms like Next.js/Remix integrated server rendering extract server code from the same page file. Serverless platforms scale to zero between traffic spikes; anecdotal risks include leaked AWS credentials and surprise billing, which drives preference for platform-managed infra.
AI-written summary · about
chapters (6)
- 0:00The frontend dream
- 1:27The backend complexity
- 3:44Serverless as a solution
- 6:10The future of DevOps
- 8:23Integrated frameworks
- 10:33Spectrum of control
related talks
27mServerless for frontend developers
51mServerless - a backend thing that gives superpowers to frontend developers
44mServerless: Giving superpowers to frontend developers
06mAn introduction to serverless
32mServerless can do that?!
04mServerless Architectures: What, why, why not, and where next?
20mWhy Serverless Architecture is Changing Software Development
53mServerless is the Abstraction We Deserve
