As a software architect, I hate serverless. Not because it doesn't work, but because it forces design constraints that cripple your application. Here's why always-on servers matter.
The discussion is off topic for the same reason web development software patterns or the benefits of choosing one language over another aren’t really relevant to the selfhosting community. Because most self-hosters don’t develop the software they host, they set up existing software. Serverless technology itself might be relevant, if there was a project using that, but how the architectural decision impacts software development is not really relevant to self-hosters.
I can’t think of a single open source / self hostable app that needed, or even had an option to deploy as a function. I have seen FaaS projects though, but they deploy to docker.
This is just an ad for “Viduli, The AI-native cloud platform”
The discussion itself is off-topic for this community anyway. Who would even think about using “serverless” for self-hosting?
Why wouldn’t serverless technologies be relevant to the self hosted community?
The discussion is off topic for the same reason web development software patterns or the benefits of choosing one language over another aren’t really relevant to the selfhosting community. Because most self-hosters don’t develop the software they host, they set up existing software. Serverless technology itself might be relevant, if there was a project using that, but how the architectural decision impacts software development is not really relevant to self-hosters.
I can’t think of a single open source / self hostable app that needed, or even had an option to deploy as a function. I have seen FaaS projects though, but they deploy to docker.
I use serverless via knative in my homelab…