Node.js in the Cloud
summary
Panel argues starting serverless often wins for quick scaling and low ops overhead, showing concrete choices: Lambda functions inside a monorepo, Amplify and AWS services for frontend/backends, and a production app running serverless with infrastructure costs less than 1% of revenue. They report a surprising recovery from a billing spike — 250 million writes that cost about $300 — and compare predictable container budgeting versus variable function pricing.
AI-written summary · about
chapters (6)
- 0:00Welcome
- 3:02Server vs serverless for Node.js
- 7:40Scalability in enterprises
- 9:44Developer experience
- 13:37Cost predictability
- 15:02Node.js for IoT
related talks
56m8 1/2 things about serverless (with Node.js)
44mServerless: Giving superpowers to frontend developers
58mServerless: Five Key Things you need to Know
20mWhy Serverless Architecture is Changing Software Development
28mServerless - the way microservices should be
09mServerless as a Competitive Advantage for Your Business
51mServerless - a backend thing that gives superpowers to frontend developers
40mThe serverless startup