How do we use Serverless Architectures on AWS Lambda
summary
Three years of running AWS Lambda in production at OpsGenie with Java, DynamoDB, SQS, SNS, API Gateway, VPC and SAM, showing a fully serverless feature launched in 2017 that handles real customer alerts, plus a 2016 pilot. Concrete wins: global DynamoDB replication via Lambda across regions, DynamoDB auto‑scale driven by streams and lambdas, and glueing Slack to OpsGenie with API Gateway triggers. Pain points: Java cold start latency, API Gateway 30s timeout, complex observability that leads to building Tundra monitoring.
AI-written summary · about
chapters (5)
related talks
40m4 Key takeaways from running Serverless on production for 4 years
31mAccelerate business innovation with serverless applications
44mServerless Architecture on Production: Good, Bad and Ugly Parts
42mAWS Lambda from the trenches
49mServerless Architectural Patterns and Best Practices
45mPatterns & practices for developing enterprise-scale serverless applications
29m2 Years, 0 Servers: Lessons learned from running a startup 100% on Serverless
01h 02mServerless in production, an experience report