Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't) (viduli.io)

submitted 3 months ago by sommerset to c/programming@lemmy.ml

9 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] sommerset 4 points 3 months ago* (last edited 3 months ago)

I dunno. Serverless could be useful in niches. But everytime I see it used it is always illeterate frontenders building full website in lambdas

[-] digdilem@lemmy.ml 4 points 3 months ago

But everytime I see it used it is always illeterate frontenders

*illiterate

[-] realitista@lemmus.org 2 points 3 months ago

🤭

[-] Feyd@programming.dev -1 points 3 months ago

and I've seen a combination of lambda, event bridge, sqs, and ECS used to great effect. Why should an entire ecosystem of tools be judged because it can be used by "illiterate frontenders"

[-] sommerset 3 points 3 months ago

All I see is react developers building full sites in lambdas in vercel.

No connection pooling, no way to warm up data, crazy slow sites typically after a single backend call.

If you use lambdas differently - that's great.

Also - ecs is NOT serverless. I have no issues with ecs

[-] Feyd@programming.dev 2 points 3 months ago

ECS not being serverless was the point. You're constructing a strawman to say an entire set of tools is useless because someone is using them badly, and that's ignorant at best and actively malicious at worst. And don't think I didn't clock that this article you posted is really an advertisement for whatever this viduli thing is.

[-] sommerset 2 points 3 months ago

Not someone, absolute majority is my point.
Just because u happened to use it properly does not mean much. People are strongly confused by serverless and should be advised against it by default.