News for hackers. Stuff that matters.
Re:Azure Functions vs. AWS Lambda – Scaling Face Off by taspeotis on Monday January 08, 2018 @04:27PM (#16100760)
“On Azure I’m using .NET 4.6 on the v1 runtime while on AWS I’m using the same code running under .NET Core 1.0.“

.NET Core has way less baggage than .NET 4.6 [1] so you’d be expecting AWS to come out ahead.

It looks like Azure functions supports .NET Core now [2]. (Edit: just noticed the author is aware of this [3].)

Of course it might also be Blob storage having higher latency than S3.

Having used Azure Functions before I agree with the article’s criticisms about scaling.

[1] https://www.ageofascent.com/2016/02/18/asp-net-core-exeeds-1... Mind this article is talking about comparing ASP.NET with ASP.NET Core, and .NET with .NET Core, not just .NET Core’s performance.

[2] https://github.com/Azure/Azure-Functions/issues/98

[3] https://www.azurefromthetrenches.com/azure-functions-v2-prev...

Re:Azure Functions vs. AWS Lambda – Scaling Face Off by karavelov on Monday January 08, 2018 @04:51PM (#16100995)
He also compares AWS Lambda with Azure blob storage backend and it still lot faster - just 25ms added latency to cross internet from AWS to Azure DC.
Re:Azure Functions vs. AWS Lambda – Scaling Face Off by oceanswave on Tuesday January 09, 2018 @07:24AM (#16105620)
It’s also difficult to run true x64 bit workloads on azure functions as it invokes the x86 version of the dotnet executable, regardless if the application is set to x64