“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

“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-15-million-requests-12-6-gbps/ 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 https://github.com/Azure/Azure-Functions/issues/98 [3] https://www.azurefromthetrenches.com/azure-functions-v2-preview-performance-issues-net-core-standard/ https://www.azurefromthetrenches.com/azure-functions-v2-prev...