all 50 comments

sorted by: hot top controversial new old
[–] 210 points 2 years ago* (2 children)

>buy serverless cloud
>look inside
>servers

  • source
  • hideshow 4 child comments
  • [–] 50 points 2 years ago* (2 children)

    >buy serverless cloud

    >never look inside

  • source
  • parent
  • hideshow 4 child comments
  • [–] 98 points 2 years ago (4 children)

    It's not serverless, it's just someone else's server

  • source
  • hideshow 8 child comments
  • [–] 30 points 2 years ago (1 child)

    Yeah, yeah, but I don't have to patch it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 years ago (1 child)

    Exactly, it is as much serverless as the offering that allowed to host php sites back in the day.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 60 points 2 years ago
    [–] 31 points 2 years ago (2 children)

    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

  • source
  • hideshow 4 child comments
  • [–] [S] 21 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 9 points 2 years ago (6 children)

    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?

  • source
  • parent
  • hideshow 9 child comments
  • [–] [S] 9 points 2 years 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.

  • source
  • parent
  • [+] 2 points 2 years ago* (last edited 2 years ago) (1 child)
  • [–] 5 points 2 years ago* (last edited 2 years ago) (1 child)

    It really depends on how much customization has gone into the site. TechCrunch, Wired, and TIME all use WordPress for example, but their theme is customized to the point where you can't really tell that it's WordPress. There are some ways to tell though, for example some of the larger sites are hosted by Automattic (these say "powered by WordPress VIP" in the footer), and /wp-admin usually still works to go to the login page.

  • source
  • parent
  • hideshow 2 child comments
  • [+] 2 points 2 years ago* (last edited 2 years ago) (1 child)
  • [+] 3 points 2 years ago* (last edited 2 years ago) (1 child)
  • [+] 1 point 2 years ago* (last edited 2 years ago) (1 child)
  • [+] 2 points 2 years ago* (last edited 2 years ago) (1 child)
  • load more comments (3 replies)
  • [–] 4 points 2 years ago (1 child)

    Yeah... Indeed, our field is pretty prone to weird tribalism and jumping on bandwagons. Still, I dislike that just as much lol

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 2 years 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.

  • source
  • parent
  • [–] 3 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago (1 child)

    see so many trends come and go

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 26 points 2 years ago (1 child)

    Eli5 server less, even on paper...

  • source
  • hideshow 2 child comments
  • [–] 28 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 38 points 2 years ago* (1 child)

    Serverless sounds like a terrible name for this lmao.

    Why not remote functions or something like that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 22 points 2 years ago (1 child)

    Marketing™️ I guess? :P

    But probably because YOU don't have to fuck around with servers, for you it's just an upload of a function.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 2 years ago (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 2 years ago* (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 years 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"?

  • source
  • parent
  • [+] 22 points 2 years ago* (last edited 9 months ago) (1 child)
  • [–] 6 points 2 years ago

    I haven't ran into a good use-case to try out server-less yet. Either cold starts would be a problem (for example, I have an endpoint that needs to load a 5GB model into RAM, and it takes about 45 seconds). Or, it's just much more expensive than a VPS if the service is projected to constantly serve many requests all day. Containerized services on a VPS doesn't require much server maintenance (unless you have a dozen or so micro-services, then yeah, Kubernetes maintenance adds a lot of overhead).

  • source
  • parent
  • [–] 18 points 2 years ago

    serverless devs are the same as devs who don't know what graceful degradation is.

    you don't have to be a server admin but at least know the basics

  • source
  • [–] 8 points 2 years ago

    But think of the profit margins, and all the buzzwords our marketing team can use

  • source