Using AWS Lambda and Azure Functions to develop serverless applications
summary
Compares AWS Lambda and Azure Functions through a concrete image-processing pipeline: a static SPA uploads to S3 via signed S3 upload URLs, S3 triggers a Lambda that calls Amazon Rekognition to detect bottles, tags object metadata, publishes to SNS and forwards to Azure for OCR and Slack alerts. Shows Serverless Framework and Node.js templates, local invoke and CloudWatch logs, deployment/rollback, and tradeoffs like Lambda 5-minute max, cold starts, VPC ENI limits, and when a VM or containers become cheaper. Serverless framework
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:23What do you do
- 2:42Why
- 3:06DomainDriven Design
- 5:07The Core Domain
- 7:04Function Programming
- 7:46Building monoliths
- 9:00Function fever
- 13:31Demo
- 16:35AWS Lambda vs Azure Functions
- 19:23Demo example
- 24:34Traditional solution
- 26:22Serverless solution
- 29:08Azure Functions
- 29:46Code
- 40:51Lambda
- 44:05Conclusion
- 46:20Costs
- 47:02Rethink Lambda
- 47:23Cost of Lambda
- 49:44Unit Tests
- 50:16In Memory Tests
- 51:01Login Monitoring
- 51:33Cloud Watch
- 52:22Service
- 53:00Tips on writing
- 56:21Lambda gotchas
- 57:52Lambda deployment limits
related talks
01h 18mBuilding applications with Serverless Framework ...
58mIntroduction to Serverless with AWS Lambda in C#
25mHow Serverless Is Changing the World for Developers
20mLost in Serverless: AWS Lambda, Google Cloud Function, Azure Functions...
58mAWS Lambda and Serverless Framework Deep dive
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
55mLive Serverless
34mPython in Serverless Architectures