4 ms·
Nobody is saying everything needs to be serverless. I'm addressing the point that going the traditional route doesn't negate the work required to implement a cu
by gochi 3y ago
Nobody is saying everything needs to be serverless. I'm addressing the point that going the traditional route doesn't negate the work required to implement a custom error page and handle rewrites on error.
- mikojan 3y agoYes they are and the promise cited as a justification is always "automatic scalability", "increased reliability", "decreased downtime". This is from the first google result on "Why move to cloud": https://www.forbes.com/sites/forbestechcouncil/2021/03/12/why-migrate-to-the-cloud-the-basics-benefits-and-real-life-examples/ https://www.forbes.com/sites/forbestechcouncil/2021/03/12/wh...
- pc86 3y agoI think a lot of people do advocate that everything be serverless, but at the very least the industry as a whole defaults to that. You now need a good reason not to deploy bleeding-edge $FRAMEWORK SPAs to serverless edge cloud functions or whatever they're called this month, rather than only using them when it makes sense.
- naikrovek 3y agoyeah there's a lot of fashion trends that this industry follows and it drives me insane. by "fashion" I mean new, hot frameworks, architectures, providers, or anything which is chosen because it looks fun or might allow some resumes to be meatier. no one makes solutions for their problems anymore, they make problems for their currently-favorite solution.
- pc86 3y agoI've been guilty of it myself in the past but I'm increasingly getting to a point, especially for side projects that I intend to make a few dollars off of, where I just want to deploy a compiled-language site to a VM and point a domain at it.