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.
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.
“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.
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.
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.
And there we have it folks, the suffix “less” is now redefined
As with everything marketing, words mean nothing they just sound cool.
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.
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.
I don’t think it is. it’s what you use if you’re serverless yourself.
“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.
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.
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.