Serverless - the way microservices should be
summary
Argues that serverless moves operations toward zero by running small AWS Lambda functions, using Claudia.js or the Serverless framework to deploy, and integrating API Gateway, SNS, CloudWatch, and DynamoDB; claims cost drops (example: 1 million free requests on AWS, companies allegedly spending <$100), shows a handler.js example and deploy commands, and notes real limits: cold starts, vendor lock-in, lack of guaranteed SLA, and simpler but different operational work.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:45ONE DOES NOT SIMPLY
- 2:43How did we get here?
- 3:13Monolith - Cons
- 5:45Microservices - Pros
- 8:26How we do microservices now?
- 8:58Communication
- 10:58Serverless - Pros
- 13:38How does serverless "kill" DevOps?
- 15:02Who are the serverless providers?
- 15:56Comparison
- 17:31Serverless architecture
- 19:18Asynchronous
- 20:02Logging
- 24:09Claudia API Builder
- 26:56Conclusion
related talks
20mWhy Serverless Architecture is Changing Software Development
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
54mYou should be building Serverless Microservices
01h 00mServerless - reality or BS - notes from the trenches
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
01h 00mMicroservices and Serverless
53mServerless is the Abstraction We Deserve
25mHow Serverless Is Changing the World for Developers
