4 ms·
If static sites are now also Serverless, the word has lost all meaning. IF I had chosen the Rails/Phoneix route, I'd need to worry about hosting imagemagick or
by icebraining 9y ago
If static sites are now also Serverless, the word has lost all meaning.
IF I had chosen the Rails/Phoneix route, I'd need to worry about hosting imagemagick or the like somewhere.
Static sites have no option but to run that stuff ahead of time, but that doesn't mean that dynamic sites can't do the same. Asset Pipelines with precompilation are pretty common - both Rails and Phoenix have one.
- cryptonector 9y ago"Serverless" is itself a bit of a misnomer. The point seems to be to distribute stateless sub-computations. Whoop dee doo. At some point you need a "server" to modify application state. A static site has no state modifications, so it actually is serverless in this sense of having stateless computation.
- neya 9y agoThanks, that was exactly what I was going to reply. Perfectly explained, thank you.
- icebraining 9y agoI get it, but while the name is not very good, there's a reason why it came about now, despite the fact that we've had static website hosting for decades. It was coined to describe a particular kind of service, and retrofitting it makes it less useful and more prone to confusion.
- not_kurt_godel 9y agoIf your static site is running on a physical or virtual host that you manage, then it is not serverless. Not a difficult distinction?
- icebraining 9y agoRight, but we've had that since the start of the web. I get that Serverless is not a very good name, but there's a reason why it was coined now - it was meant to describe a particular kind of service that appeared recently. If we're going to apply it backwards to any web hosting service where the host was not explicitly managed, the term becomes much less useful.
- not_kurt_godel 9y ago> If we're going to apply it backwards to any web hosting service where the host was not explicitly managed But that's the thing - there is no "the host" any more. In the days of yore, if the physical machine hosting your site failed, your site went down. Maybe some rare services had failover and redundancy to some degree, but they were primitive at best compared to AWS (and the other serverless providers, for that matter) today. There was simply no comparison to the ecosystem that exists today. Have you ever had to manage production hosts before? It simply boggles my mind how many people throw out these "the cloud is just somebody else's computer" comparisons - like they've never had to diagnose JVM garbage collection thrashing at 3 in the morning before, or dealt with a server that goes down due to 100% of disk space being consumed by logs, or patch a massive fleet in a matter of hours in response to a CVE, or a power outage, or a hyper-localized network event in a data center, or any of the other million+ super annoying problems that come with managing physical hosts, and to a large degree, VMs/VPSes.
- icebraining 9y agoI can't tell if you're agreeing or disagreeing with me :) my point is exactly that: what AWS et all are offering now is not like what we used to have, so we should use the term "serverless" for stuff we already had, like fully-managed static sites.
- not_kurt_godel 9y agoHa, I thought I was disagreeing, but having gone back and re-read just now, I realize I must have misread because, yes, I agree with you 100%. I was also partially expressing general grist at the naivetë of some of the other commenters.