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.
On the contrary, lots of us write our own scripts and programs. And when considering how to self host that software, serverless is a perfectly valid choice.
Just because many self hosters are hobbyists who are only capable of using things off the shelf doesn’t make self hosting infrastructure outside the scope of… selfhosting lol
I’ll rephrase it more clearly then. Selfhosting focuses on the hosting aspect of software. !programming@programming.dev focuses on the development aspect of software. This article talks about the architectural decision made during development. It doesn’t talk about how to host serverless. It doesn’t even talk about why you wouldn’t want to selfhost serverless. It talks about bad software patterns the come with serverless. It also talks about the cost of running those things but even that is geared more towards enterprise level devops people.
It might be an interesting read from the software developer perspective but it’s not interesting from the selfhoster perspective, because the article has nothing to do with selfhosting.
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.
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.
On the contrary, lots of us write our own scripts and programs. And when considering how to self host that software, serverless is a perfectly valid choice.
Just because many self hosters are hobbyists who are only capable of using things off the shelf doesn’t make self hosting infrastructure outside the scope of… selfhosting lol
I’ll rephrase it more clearly then. Selfhosting focuses on the hosting aspect of software. !programming@programming.dev focuses on the development aspect of software. This article talks about the architectural decision made during development. It doesn’t talk about how to host serverless. It doesn’t even talk about why you wouldn’t want to selfhost serverless. It talks about bad software patterns the come with serverless. It also talks about the cost of running those things but even that is geared more towards enterprise level devops people.
It might be an interesting read from the software developer perspective but it’s not interesting from the selfhoster perspective, because the article has nothing to do with selfhosting.
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.