Go Serverless!
summary
Explains how to run full Go web frameworks like Fiber on AWS Lambda by using an adapter (aws-lambda-go-api-proxy), keep one codebase of modular commands (each a normal Go app) and point SAM functions to those command folders so you deploy apps not tiny functions. Shows using AWS SAM with samconfig profiles for multi-stage deploys, adding Chromium as a Lambda layer, and tradeoffs: vendor lock, framework cold-start overhead, and memory→vCPU billing quirks.
AI-written summary · about
chapters (8)
- 0:00Go Serverless intro
- 1:57Consider serverless architecture
- 7:52Single-function limits
- 9:15Apps not functions
- 15:13Deploy to AWS SAM
- 21:54AWS SAM dev cycle
- 26:04When serverless fits
- 30:21Q&A
related talks
52mGo and AWS Lambda – a perfect Match
39mHow to Go with AWS Lambda?
04mServerless applications, Microservices, AWS
25mLeveraging Serverless in Full-stack Development
46mServerless Architecture Patterns and Best Practices
39mServerless Developer Experience with AWS SAM
51mTaking Serverless to the Next Level
31mAccelerate business innovation with serverless applications
