Community interview
summary
Argues that serverless cuts cost when idle but can become more expensive as traffic grows, summarises practical tooling and community tactics: you don't pay if not used as the billing claim, recommends AWS SAM and Azure Functions for hands‑on work, points to podcasts (20 episodes of Serverless Chats) and books, and describes meetup logistics using Slack and Trello plus sponsorship for venues. Organising strain is mainly time, mitigated by distributing tasks—now six co-organizers run the meetup in Berlin.
AI-written summary · about
related talks
01h 00mServerless - reality or BS - notes from the trenches
34mPitfalls and insights in mastering serverless API-driven architecture
41mWhy the fuss about serverless
56m8 1/2 things about serverless (with Node.js)
28mFun With Serverless Javascript
49mYou Don't Want Serverless
28mThe Brave New World of serverless computing
51mConfusion In The Land Of The Serverless