Refactor your .NET API to Single Purpose Lambda Functions

Hi, I'm James. In this video, we will look at how you can modernise a simple Web API built with .NET Framework to run on AWS Lambda.

In the last video we look at how you can take an existing ASP.NET API with multiple endpoints and refactor to that to use a single purpose AWS Lambda function for each individual endpoint.

00:00 - Introduction
01:10 - Why refactor?
01:55 - Revising the example app
02:25 - Lambda Annotations Framework
03:05 - Startup Code
04:10 - Lambda API Endpoints with Annotations Framework
08:10 - Function Handler String changes
11:30 - Deploy & Test

Links

[sergeykichuk]

Thanks for the video, useful info. Please post more on serverless more comprehensive scenarios with CI/CD

[CraigSmitham]

While I see some of the benefits of this approach, what about cold starts? With a single lambda function serving an API, it can easily share the same pool of provisioned lambda concurrency. With separate lambdas for each endpoint, if you want pre-provisioned concurrency, you would have to do that for every function. Thoughts?

[vivekgowda]

Can we create one function for one controller method instead of creating it for each API endpoint? is this possible?