20
Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't) (viduli.io)
submitted 10 months ago by to c/programming@beehaw.org
5 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 10 months ago (1 child)

This reads as if someone doesn't understand cloud compute, iac, and so on, and just got frustrated trying to learn and explore the paradigm.

That's fine, but blaming "serverless" or aws lambda is like blaming a multicore cpu for having to learn threads and subprocceses.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 10 months ago (1 child)

    Everytime I see serverless used - it's always some illiterate frontender building next.js on lambdas. Always slow as molasses, always inflexible af.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months ago

    It sounds like the problem you describe is not with the concept of using serverless/faas cloud compute and adjacent services, but with the design and implementation done by some engineers you work with. That may be due to time constraints, lack of familiarity, engineering skill, or some other reason.

    I've seen terrible containers, terrible vms, terrible bare metal servers. I've written good and bad myself. And yes, I've seen (and done) great implementation of serverless. It's all just tools to be used.

  • permalink
  • fedilink
  • source
  • parent