"To me, a Function as a Service is all about running application functions, so function in a context, when needed on a serverless runtime. Usually what happened after this phrase is, now what is a serverless anyway? Which is a good question. To me, serverless means it's an execution model. It's how you run code without having to care about servers."
"The extremely important part about this is also allocating resources when you need them. Meaning you don't pay for something that's not running and you'll only use something when you don't need to, which is pretty cool when everybody is generating images with GPUs. Function as a Service is different from serverless. I just want to put that out there because I have lots of people that are saying it's the same thing. Function as a Service is a subset of serverless."
Function as a Service runs application functions in context on a serverless execution model that allocates compute only when needed. Serverless is an execution model that lets code run without managing servers and emphasizes dynamic resource allocation to avoid paying for idle resources. Function as a Service is a subset of serverless focused on executing small, specific pieces of code within broader application contexts. Allocating resources on demand becomes critical with resource-intensive workloads like GPU-generated images. A robust FaaS runtime separates runtime capabilities from function definitions, enabling better scaling, isolation, security, and operational control. Wasm components and wasmCloud provide modular, portable building blocks to implement such runtimes.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]