*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

a cat looks intrigued but co fused at the camera.Text says "Serverless API? I look inside. What do I see? Servers". Small text all around the cat says "boneless chicken. never had any btw", "literally why is it called serverless if there are servers", "uf it wouldn't have servers, woukd it be local?", "can I run qwen 3.5 locally?", "just say that it has servers!", "this doesnt make any sense!". text in bottom right coner "edited by Maria on Lemmy"

all 25 comments

sorted by: hot top controversial new old
[–] 24 points 9 months 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.

  • source
  • [–] 21 points 9 months ago* (13 children)

    what is serverless api? is it local?

  • source
  • hideshow 13 child comments
  • [–] 45 points 9 months ago (3 children)

    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”.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 8 months ago* (last edited 8 months ago) (2 children)

    The moment I realized AWS Lambda is a scam was the moment I learned that you have to check if you need to clean up your runtime environment at function start, because it will sometimes reuse the same server between runs, because it's a server that they don't even bother to have behave as if it isn't.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 35 points 9 months ago (8 children)

    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.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 20 points 9 months ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -6 points 9 months ago* (1 child)

    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 🤣🤣🤣🤣

  • source
  • parent
  • hideshow 1 child comment
  • [–] 16 points 9 months ago (3 children)

    Is my delivered pizza flourless, because i don't deal with the flour and just get the pizza?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 9 months ago* (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 9 points 8 months ago* (last edited 8 months ago) (2 children)

    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.

    Someone always has to think about the server, but in serverless that someone isn't you.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 8 months ago

    Except that you do still have to think about them, because the fact that they're still just servers means that they can and will have outages. They also tend to be insanely expensive on relative compute cost compared to a server that you still call a server, which means a lot more thinking about your budget.

  • source
  • parent
  • [–] 1 point 8 months 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

  • source
  • parent
  • [–] 3 points 8 months ago*

    > NOSQL
    > Look inside.
    > SQL... and not only that, bunch of other stuff too.

  • source
  • [–] 2 points 9 months ago

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

  • source
  • [–] 1 point 9 months 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.

  • source
  • [+] -7 points 9 months ago (2 children)