• I’m as critical as the next guy of how overused and abused serverless/microservice architectures can be, but there’s disliking something and being completely disingenuous. Some of the comments every time the subject is even remotely mentioned fall into the latter. This time is not the exception lol

    •  gkd   ( @gkd@lemmy.ml ) OP
      link
      fedilink
      1511 months ago

      I mean that’s generally the case with most tech. Just like the never ending PHP hate. Plenty of reasons to dislike or not use it but no reason to think it’s the scum of the earth.

      • On a tangent, I imagine PHP is still one of the most used backends. Wordpress uses PHP and I wouldn’t be surprised if 50% or more of the websites I visited are Wordpress sites. So I guess many others experience the same?

        •  gkd   ( @gkd@lemmy.ml ) OP
          link
          fedilink
          711 months ago

          Very widely used still and well maintained. It’s been a good options since 7 came around. Most of the hate IMO comes from people who were working with PHP4/5 code or people who just saw PHP4/5 code and think that’s what the language is today.

        •  gkd   ( @gkd@lemmy.ml ) OP
          link
          fedilink
          111 months ago

          For sure. People find a niche they like and then think that is the solution to any problem. Until, of course, some new shiny tech catches their eye and they try that out (or their favorite clickbait Medium writer comes out with an article about “Why you shouldn’t be using ____ anymore in 2023”). Then the love of their life gets thrown to the curb.

    •  catacomb   ( @catacomb@beehaw.org ) 
      link
      fedilink
      English
      411 months 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.

        •  catacomb   ( @catacomb@beehaw.org ) 
          link
          fedilink
          English
          211 months 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   ( @dan@upvote.au ) 
            link
            fedilink
            1
            edit-2
            11 months 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.

    •  0xD   ( @0xD@infosec.pub ) 
      link
      fedilink
      19
      edit-2
      11 months ago

      Instead of spinning up a classical server like Apache or IIS for what you need, you just write a single function that you can bind to an endpoint and just host that - the rest is abstracted away from you.

          •  DrM   ( @DrM@feddit.de ) 
            link
            fedilink
            811 months ago

            I think that’s the main reason, it’s a good name explaining what you can expect: an environment where you don’t have to worry about servers and don’t need an administrator

            •  dan   ( @dan@upvote.au ) 
              link
              fedilink
              6
              edit-2
              11 months ago

              Why not just call it shared hosting though? It’s essentially the same concept as getting a GoDaddy (or Bluegost or whatever) hosting account and uploading a PHP file lol

              •  DrM   ( @DrM@feddit.de ) 
                link
                fedilink
                511 months ago

                Shared hosting sounds like you don’t have your data stored privately and doesn’t sound like less work for the company.

                Don’t look at the name from a technicians perspective, but from the perspective of a manager of a small startup who wants to reduce the overhead for hosting it’s service as much as possible. Also serverless is not wrong per sé, it’s exactly what you as the customer get.

                You could spin it the same way for every other instance. Why do you call GoDaddy “shared hosting”, in the end it’s just a pod on a kubernetes cluster. So why don’t you call it “private kubernetes pod”?