• Allah@lemmy.world
    16·
    2 days ago

    page 196 of CompTIA Security+ SY0-701 Cert Guide

    Serverless

    Another popular architecture is the serverless architecture. Be aware that serverless does not mean that you do not need a server somewhere. Instead, serverless archi- tecture involves using cloud platforms to host and/or to develop code. For example, you might have a serverless app that is distributed in a cloud provider like Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). Serverless is a cloud computing execution model in which the cloud provider (AWS, Azure, Google Cloud, and so on) dynamically manages the allocation and provision- ing of servers. Serverless applications run in stateless containers that are ephemeral and event triggered (fully managed by the cloud provider). AWS Lambda is one of the most popular serverless architectures in the industry.

    • lightnsfw@reddthat.com
      17·
      2 days ago

      Me before opening this thread: I bet it’s a weasel term for cloud bullshit.

      Fucking marketing dickheads.

  • umbraroze@lemmy.world
    541·
    3 days ago

    I was under the impression that “serverless” was marketing speak for “it has servers, but it’s more opaque, and we will charge you a lot more”.

    • merc@sh.itjust.works
      38·
      3 days ago

      It’s more like “it has servers, but you don’t have to manage them, or hire someone to manage them, and we will charge you a lot more, but maybe you’ll save money because you don’t have to hire someone”.

      • merc@sh.itjust.works
        41·
        3 days ago

        Not really. Serverless is OpEx. VPS is OpEx, but you also need OpEx budget for a person who can manage servers, not just a programmer.

        VPS isn’t rocket science, so you can probably find someone who can both program things and do the basic VPS server management needed. But, it is work that needs to be done by someone. In some cases, like if you’re hiring scientists from academia who have never done any of their own sysadmin type stuff, it might be easier to just go with serverless so all they need to do is write programs.

      • GreenKnight23@lemmy.world
        23·
        3 days ago

        an oversimplification of a complex solution.

        it’s like eating at a restaurant and bitching it’s like eating at home.

        while true, at home you didn’t need to pay for the staff, stove, ingredients, pots, pans, water, flatware, plates, cups, etc… you also ignore the fact that your kitchen at home is comprised of a single 200w microwave, a minifridge, and a single plate.

  • ExcessShiv@lemmy.dbzer0.com
    1116·
    3 days ago

    I mean, “serverless computing” has always only meant that it’s “serverless” for the customer who buys the compute power in the sense that they don’t have to bother the slightest with the architecture or managing it. Not really anything to reveal there…

      • Farid@startrek.website
        102·
        3 days ago

        I think the “Cat Looks Inside” meme would’ve been more appropriate, because the “Let’s See Who This Really Is” (a.k.a. “Scooby Doo Reveal”) meme is more about revealing something that is actually different, while CLI is sarcastic. Like “Wireless device. Look inside. Wires” isn’t revealing anything serious but makes fun of the misleading nomenclature. A good SDR example would be pulling the mask off a KKK member to reveal a cop, while they are supposed to be on the opposite sides, they are one and the same.
        On the meme spectrum, SDR sits somewhere between CLI and “They are the Same Picture”.

        Thank you for not coming to my MemTalk.

      • rumba@lemmy.zipEnglish
        142·
        3 days ago

        MySQL: you set it up, if the server fails, you have to fix it. You set up replication, replication fails, you have to fix it. It’s your alarms, you get up at 2:00 a.m., you set up backups. You deal with IP changes. You deal with your two+ boxes and their patches. Those servers are your responsibility. If their hypervisor needs an update you’re stuck with the boxes going down.

        Aurora serverless: you don’t deal with any of that.

        Saying they’re the same as like saying that a self-driving taxi is the same as leasing your own car. In both cases there are servers involved, But in one of the two cases you don’t have anything to do with the server.

            • aesthelete@lemmy.world
              81·
              3 days ago

              Serverless in cloud computing typically refers to ephemeral processes…things like lambdas and message handlers.

              Outside of that it’s just a buzzword anyway (like “low code/no code” which is similar) so I guess any managed software is serverless by your definition?

        • aesthelete@lemmy.world
          62·
          3 days ago

          Saying they’re the same as like saying that a self-driving taxi is the same as leasing your own car.

          No saying serverless computing is serverless–which has several definitions btw like all marketing doublespeak–is like saying a taxi is driverless.

        • NotSteve_@lemmy.ca
          1·
          3 days ago

          Haha I know, parts of the software I work on uses serverless infrastructure. I’m just kidding

      • merc@sh.itjust.works
        51·
        3 days ago

        From the point of view of the customer it is serverless. Maybe it’s being done on a server, but maybe it’s a magical genie in a bottle. You don’t have to care because from your point of view you upload code and that code magically runs.

        This fits perfectly in with other “-less” words. Like many “priceless” museum artifacts were bought and sold before they showed up in the museum. To the visitor and maybe to the museum they’re priceless, but to the dealers who found it for the museum it had a price.

        • TrickDacy@lemmy.world
          21·
          2 days ago

          Maybe it’s being done on a server, but maybe it’s a magical genie in a bottle. You don’t have to care because from your point of view you upload code and that code magically runs.

          Hard disagree. As someone who wrote several AWS lambdas, I know you have to care that it’s being run on a server and you have to adjust to your code to work within that very-specific server system.

          If anything it should be called “poly-server” because you cannot write your code without considering that it can be executed from several servers around the same time. I don’t buy what you’re selling here, other -less examples don’t seem to betray their terminology at all to me but “serverless” will always sound wrong to me.

      • dx1@lemmy.world
        31·
        3 days ago

        “Function-based”, “image-based” would have been slightly more accurate terms.

        Wireless devices aren’t actually “free of wires”, it’s that you don’t have to deal with wires (or significantly less, since you still have to charge them etc., save for wireless charging). So that’s not really new either.

        • TrickDacy@lemmy.world
          1·
          2 days ago

          The first time I heard the term wireless, I was a little kid and I understood very quickly. When I first heard the term “serverless” I was an adult who had been programming a couple years. I remember genuinely being confused as strings of unparseable buzzwords bounced off my brain. A minute or two into the explanation, I’m pretty sure I said “oh, so it actually does run on a server”. The ops person was forced to say yes. It was a genuinely confusing and imo pointless conversation that we shouldn’t have needed to have.

          • dx1@lemmy.world
            1·
            2 days ago

            Were you doing any serious “devops” at the time? I didn’t struggle with “serverless” knowing that otherwise I had to manually provision servers, virtual or bare metal.

    • jol@discuss.tchncs.de
      11·
      3 days ago

      This naming also came from a time when most people bought/rented servers where they would SSH/FTP into to update their software.

      • merc@sh.itjust.works
        3·
        3 days ago

        Yeah, and the big selling point for serverless is that you only deal with the code you want to run, none of that “server management” stuff. It’s a perfectly reasonable name based on what’s appealing about it.

      • ricecake@sh.itjust.works
        3·
        3 days ago

        People used “function as a service”, “managed *” or “compute as a service” for a bit, but serverless actually seemed to capture the gist of it for customers better. It may be marketing speak, but it does seem to be an effective shorthand for the value it provides.

        • bleistift2@sopuli.xyzEnglish
          7·
          3 days ago

          In computer science, “transparent” means that you don’t see something, i.e. internals are hidden. Like you don’t see glass.

    • gencha@lemm.ee
      4·
      3 days ago

      You can install serverless frameworks on your server though. Best of both worlds

      • samtoxie@sh.itjust.works
        8·
        3 days ago

        As someone in the ISP/hosting business, i can tell you that there are plenty of companies incapable of sufficiently managing actual servers. For their own safety it’s probably better to let someone else manage it for them (despite getting ripped off then)

        • Hackworth@lemmy.worldEnglish
          8·
          3 days ago

          I’d like to take the stance that: If you can’t manage your own data, don’t start a business. But that seems like a shaky foundation to plant a flag, so I will instead say, “I hate Oracle.”

          • merc@sh.itjust.works
            21·
            3 days ago

            I agree, and If you can’t manage your own health, don’t be alive, which is why the world should consist 100% of medical doctors.

        • Suzune@ani.social
          5·
          3 days ago

          If they cannot manage their own infrastructure, they also don’t know what infrastructure is needed for their services. And they won’t even have the opportunity to learn anymore.

          Secondly, if you buy external services, you need to consider improving connectivity.

          I mean, you can still work on your on-premises servers, if your internet connection fails. You cannot, if you outsourced essentials parts.

  • just_an_average_joe@lemmy.dbzer0.comEnglish
    725·
    3 days ago

    This is what happens when a technical field gets infiltrated by business bros. Remember how openai was talking about AGI helping humanity or smth? Their definition of AGI was leaked recently, its “making $100 billion profit”.

    That’s it, thats what will help humanity achieve its true potential, by openai making $100b in profits.

    • prole@sh.itjust.worksEnglish
      312·
      3 days ago

      That’s it, thats what will help humanity achieve its true potential, by openai making $100b in profits.

      Yay capitalism! We did it!

    • merc@sh.itjust.works
      7·
      3 days ago

      Not really. Serverless is “you don’t need to manage the servers”. For some businesses, even managing a VPS is too technical a task. So, you could either go out and hire someone who can do that, or you can go serverless and pay a bit more for that, but save by not needing additional expertise.

      • just_an_average_joe@lemmy.dbzer0.comEnglish
        23·
        2 days ago

        We all are disagreeing on the naming not the functionality. It used to be the case that names in tech were descriptive, just by reading it out loud you can understand the tech (e,g. SQL, OOP etc.).

        “Serverless” is a marketing term. A better name would be “server agnostic deployment” or many many other ways to describe it.

        The fact is, this name was created by the people selling it not the people using it. And i am sure the idea is not new, but the serverless name tries to make it seem like a comparatively recent thing so people would buy it more.