The Real Cost of Pay-Per-Use in Serverless
no recording on file
summary
Examines cost drivers of serverless pay-per-use billing (e.g., function execution time, external API latency, bugs causing runaway invocations) and how those make monthly budgeting and monitoring difficult. Discusses concrete issues that inflate bills in platforms like AWS Lambda-style serverless and what to monitor to detect and control unexpected charges.
AI-written summary · about
related talks
34mPitfalls and insights in mastering serverless API-driven architecture
58mServerless: Five Key Things you need to Know
42mFaaS or not to FaaS: Visible & invisible benefits of the Serverless paradigm
49mYou Don't Want Serverless
27mSite Reliability in the Serverless Age
41mServerless systems that won't burn a hole in your pocket
28mWhat We Should All Worry About When Monitoring Serverless Applications
01h 00mServerless - reality or BS - notes from the trenches