No Side JavaScript and the serverless Revolution
summary
Argues that modern serverless apps — dubbed no-side JavaScript — run as event-driven AWS Lambda functions (cold starts measured in milliseconds, 50 MB upload / 250 MB expanded package limits, default 1,000 concurrent soft limit, max 5 minute timeout, Node runtimes v4/v6 so no async/await on Lambda) and require small, single-purpose functions, external state (S3/DynamoDB), and read-only file handling. Recommends using the Serverless Framework (npm i -g serverless; serverless create && serverless deploy) to wire Lambdas, API Gateway, S3, CloudFront and automate deployments.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:45The serverless revolution
- 3:38JavaScript and serverless
- 6:18Serverless
- 10:13What serverless says
- 14:17No HTTP server
- 19:32Readonly file system
- 27:05Concerns
- 28:35Serverless Framework
- 29:20CLI
- 30:28What serverless does
- 32:05Getting started
- 33:09Learn more
- 34:15Use cases
related talks
28mServerless - the way microservices should be
29m2 Years, 0 Servers: Lessons learned from running a startup 100% on Serverless
25mHow Serverless Is Changing the World for Developers
56m8 1/2 things about serverless (with Node.js)
20mWhy Serverless Architecture is Changing Software Development
25mA Decade of Modern JS and the Rise of Serverless Fullstack
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
12mServerless State of the Union