No, I don't need servers for .NET development in AWS!
summary
Shows a C# serverless architecture on AWS that is actually runnable: Lambda + API Gateway + Cognito (hosted UI) + DynamoDB with single-table design, SQS/SNS/EventBridge for messaging and X‑Ray for tracing. Calls out specifics: Lambda cold starts and 15‑minute timeout, use of provisioned concurrency to avoid them, DynamoDB partition limits (≈10 GB per partition, ~3,000 RCUs) and access patterns, and demo of Swagger+Cognito that authenticates and successfully calls the API. Talks costs, SDK choices and concrete design patterns.
AI-written summary · about
chapters (13)
- 0:00Serverless .NET on AWS
- 1:39Serverless buzzword
- 3:43Reactive serverless apps
- 8:59Event-driven AWS
- 10:27AWS Lambda for .NET
- 15:43Lambda cold starts
- 20:18DynamoDB for serverless
- 31:38Single table design
- 38:40Cognito identity
- 43:32Demo: Secure APIs with Cognito
- 46:52API Gateway bridge
- 50:06Monitoring with X-Ray
- 51:35Q&A
related talks
40mThe serverless startup
49mServerless Architectural Patterns and Best Practices
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
53mLook Ma! No servers!
47mAdvanced Serverless Architectural Patterns on AWS
54mServerless Architectures: no servers allowed!
39mThink in Cloud, Develop in Cloud
58mIntroduction to Serverless with AWS Lambda in C#