Going Serverless
summary
Teams report concrete wins and limits: BBC runs ~2.5 billion Lambda executions/month and used serverless for label extraction of ~200 new iPlayer episodes/day but rewrites the workflow when updates went stale; K15T runs production functions for JIRA webhook spikes of thousands of invocations in seconds for two years; Walmart builds an agnostic platform using OpenFaaS/Knative across clouds. Common problems: cost thresholds, need for Zipkin/Jaeger tracing, vendor lock‑in, Lambda@Edge and API Gateway for latency, and custom tooling to pull logs and deploy functions.
AI-written summary · about
chapters (7)
related talks
47mServerless in production, an experience report
01h 00mServerless - reality or BS - notes from the trenches
01h 02mServerless in production, an experience report
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
31mAccelerate business innovation with serverless applications
42mAWS Lambda from the trenches
39mServerless in production, an experience report
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
