As a software architect, I hate serverless. Not because it doesn't work, but because it forces design constraints that cripple your application. Here's why always-on servers matter.
  • Feyd@programming.dev
    2·
    3 days ago

    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?

    • Fair Fairy@thelemmy.clubOP
      4·
      3 days 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

      • Feyd@programming.dev
        22·
        2 days 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”

        • Fair Fairy@thelemmy.clubOP
          3·
          2 days 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
            21·
            2 days 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.

            • Fair Fairy@thelemmy.clubOP
              2·
              2 days 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.