13
Serverless Is An Architectural Handicap (And I'm Tired of Pretending it Isn't) (viduli.io)
submitted 10 months ago by 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
[–] 2 points 10 months ago (1 child)

This person doesn't seem to know you can have both serverless components and servers working together to use whatever is appropriate for different parts of an application?

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

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -1 points 10 months ago (1 child)

    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"

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

    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

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

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •