Live data from Hacker News

.NET Core Web API on AWS Lambda Performance

cloudncode.blog

21–22 of 22 posts

Re: .NET Core Web API on AWS Lambda Performance

#21
post #4

Just worth pointing out that Azure (Microsoft's cloud platform) also has a Serverless option in the form of a cloud platform capability called "Azure Functions". So check out the competitor here: https://azure.microsoft.com/en-us/services/functions

Thanks! I have been using webjobs for a while and found the experience a bit scattered and subpar(especially the scheduling). Hopefully azure functions are better in this regard.

We've been using Functions for about a year now with great success. You can access nuget, code in a bunch of languages, and trigger in a bunch of ways. Also, you can write them from visual studio and then deploy to azure if you're doing something fancy and don't enjoy debug'n in Azure.

Re: .NET Core Web API on AWS Lambda Performance

#22
Spin up time of WebAPI is shown here, but returning hard coded values isn't much more than a proof of concept. Once you connect to data, you have to look at spin up time of something like EF and context/model generation over and over. What happens when you get 20 controllers with many function and routing actually has to do some work.

Lambda also prevents any long running optimization such as output cacheing.

Post reply on HN