Christian Weyer

🔮
If #AzureFunctions is not going to embrace and adopt light-weight #WebAssembly (#Wasm #WASI #WebAssemblyComponentModel)-based approaches for modern #Serverless #FaaS ASAP - it is going to be irrelevant for new projects within 2 years.

👇🏼
Dear Azure Functions team: act now!

#dotnet

Jan 21, 2023 at 8:59amWeb
Show threadmxJan 21, 2023
@christianweyer could you elaborate what you mean by that or point me to a resource to read more about your thought? I understood WebAssembly as a technology running in the browser mostly to power front ends and was using Azure Functions as technology to process and serve data. So I don't understand how this connects. Thank you!
Show threadChristian WeyerJan 21, 2023

@mx #Wasm will be a very big thing, beyond the browser. Read up on #Wasi especially. Have look at Fermyon Spin to get some ideas.

Maybe this also helps to get a start:
https://www.wasm.builders/thomastaylor312/why-webassembly-belongs-outside-the-browser-331a

Why WebAssembly Belongs Outside the Browser

by Matt Butcher, Connor Hicks, and Taylor Thomas As employees of 3 different WebAssembly (Wasm)...

Wasm Builders 🧱
Show threadmxJan 21, 2023
@christianweyer very interesting! Thank you!
Show threadTomasz PęczekJan 21, 2023

@christianweyer

💯

Fermyon Cloud is showing that this is an interesting direction. There is already some investment in AKS, so it would be great to see the same happening for Azure Functions.

I'm also wondering how much could be done just on top of Custom Handlers (https://learn.microsoft.com/en-us/azure/azure-functions/functions-custom-handlers).

Azure Functions custom handlers

Learn to use Azure Functions with any language or runtime version.

Show threadIrongutJan 21, 2023
@christianweyer I'd be interested to hear why you think that. My Azure Functions do not need WASM and I don't think it would improve their work as a mobile app backend. They are already lightweight, fast and cheap.