*the image of cat and the green > symbols were there before I edited the image

I was feelin lazy, so here we go, have a post-

should probably post more, i feel good doin things.

anyway— i hope u are doing well! <3

  • NigelFrobisher@aussie.zone
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    16 hours ago

    Had an argument with my architect about this once. He said its because serverless functions can be run on the edge as well, making them totally portable. I said that already exists and it’s called fucking executables.

    • tiramichu@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      41 minutes ago

      The real meaning of ‘serverless’ isn’t that there’s no server, but that the server is outside the scope of what you have to think about.

      The least abstracted level is bare metal. You provision the server, install an operating system, and manage system level dependencies and security updates and all of it yourself.

      Then virtual machines, where you manage the VM but not the host it runs on.

      Then containerisation where you manage the container and dependencies, but no longer have to think about the OS or the OS security updates.

      Then finally serverless, where you as an engineer concern yourself primarily with only the code, and the platform takes care of the rest.

      So it sounds kinda weird as a name, but the intent is right, because it’s all about where the boundary of responsibility is drawn.

      • tiramichu@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        39 minutes ago

        The real meaning of ‘serverless’ isn’t that there’s no server, but that the server is outside the scope of what you have to think about.

        The least abstracted level is bare metal. You provision the server, install an operating system, and manage system level dependencies and security updates and all of it yourself.

        Then virtual machines, where you manage the VM but not the host it runs on.

        Then containerisation where you manage the container and dependencies, but no longer have to think about the OS or the OS security updates.

        Then finally serverless, where you as an engineer concern yourself primarily with only the code, and the platform takes care of the rest.

        So it sounds kinda weird as a name, but the intent is right, because it’s all about where the boundary of responsibility is drawn.

        There’s always a server under the hood, and someone always needs to think about it, but in serverless that someone isn’t you.

      • kunaltyagi@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        I’ll have oversimplification for 10 dollars please.

        Virtual Machine: looks into, needs machines Cloud: looks into, is just renting Containers: looks into, we’re now shipping the devs laptop Server less: looks into, has servers. Loft of them

  • hazel@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    21
    ·
    1 day ago

    Just like so many “no code” solutions that only become truly useful once I figure out how to expose and modify the obfuscated code. But I don’t talk about Microsoft anymore.

  • AllHailTheSheep@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    17 hours ago

    the term is incredibly stupid. however, serverless services like cloud run are super cool in that you can scale down to 0, which makes it ideal for things that only get used once in a while. the containers only take 2 or 3 seconds to spin up as well, and the no config scaling support is pretty nice.

    • panda_abyss@lemmy.ca
      link
      fedilink
      English
      arrow-up
      45
      ·
      1 day ago

      No, it’s an API where on requests a server is started up to run your code.

      You don’t run the server, someone else does — hence “serverless”.

    • chisel@piefed.social
      link
      fedilink
      English
      arrow-up
      33
      ·
      1 day ago

      The concept is that you basically upload code directly to the hosting service, then set up an endpoint that points to the code, and magically run it. “Serverless” because you never deal with server setup/config/load balancing/etc… And can pretend that your code runs on nothing if you so please.

      • festnt@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        18 hours ago

        it’s also the same situation with wireless devices. it’s not that there are no wires, it’s that you don’t have to deal with any wires

      • rtxn@lemmy.world
        link
        fedilink
        English
        arrow-up
        17
        ·
        1 day ago

        Like saying that a Dockerfile or compose.yaml is “containerless” because you don’t have to manually provision a container?

        The future is fucking stupid.

        • Retail4068@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          1 day ago

          No, nerds actually getting riled up over the pedantics of this naming scheme is the sad thing. Like honestly, it’s a hoot watching you all get riled up over the pretty decent and descriptive name.

          REEEEEEEEEEEEEEEEEEEE THE SERVER IT’S REALLY THERE, IT’S JUST OBFUSCATED 🤣🤣🤣🤣

  • Xerxos@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    23 hours ago

    Of course it’s called serverless because there are less servers! /s