• catacomb@beehaw.org
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 year ago

    I think it’s a maturity thing. You eventually see so many trends come and go, peaks and troughs of hype cycles and some developers (probably including yourself at least once!) overusing certain new tech.

    You eventually discover what works with current tech and then you can become healthily critical of anything new. You see it more for where it can fit and where it can’t.

    If you have something small and stateless then serverless is easy and, more importantly, scalable. It was a little easier to see its role once the hype fog had lifted and I had a problem to solve with it.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      see so many trends come and go

      It’s interesting how things are cyclical. Serverless functions remind me of cgi-bin scripts.

      • catacomb@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Yep, it’s usually an existing idea with progression in a few areas. You could definitely achieve serverless with a cluster of servers hosting the same scripts in cgi-bin and I think that context helps to put it into perspective.

        • dan@upvote.au
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          I feel like I should start a “serverless” startup that’s just Apache running in a Kubernetes cluster with a bunch of cgi-bin scripts in a Ceph cluster. Boom, serverless with high availability.

          • folkrav@lemmy.ca
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            If you only focus on the concept of a serverless function and forego 99% of the other stuff, yeah 😛