Lambdas, Functions, Clouds, Oh My
summary
Compares how AWS Lambdas, Google, Azure and Oracle implement functions as a service with concrete tradeoffs: languages: Java, Python, Node.js, C# are widely supported, runtime shapes (zip vs custom container), and how many providers build each function into a Docker image while others accept zip uploads. Notes tooling: web editors and IDE plugins plus CLI, and local frameworks like Functions Framework, Azure Functions Core, FN for testing. Flags operational differences—cold starts, vendor lock-in through ecosystem services, and Azure’s durable functions for stateful workflows.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 3:59Evolution of application hosting
- 8:13Function as a service explained
- 14:10Leading FaaS providers overview
- 15:57Method signatures and examples
- 20:33Language support across platforms
- 23:43Web editors and prototyping
- 27:15IDE integration for functions
- 31:08Local development and testing
- 32:34Final thoughts and key considerations
- 44:00Performance and caching concerns
- 45:40Q&A session
related talks
20mLost in Serverless: AWS Lambda, Google Cloud Function, Azure Functions...
58mServerless Under the Hood
01h 02mExploring Serverless Options for .NET in Azure, AWS, and Beyond
41mContainers or Serverless Functions - When to choose what?
01h 08mUsing AWS Lambda and Azure Functions to develop serverless applications
03h 00mAWS vs GCP vs Azure
47mServerless in the Cloud (...)
41mGo for serverless functions