31–40 of 70 posts
So there's no servers, anywhere in this? You don't run it on a computer or anything? Clearly I'm being a smart ass, but pointing out that 'serverless' is an idiotic marketing term.
'Serverless' heh... oh man marketing is great. Just like if you have it in the cloud it's 'hardwareless' right?
I don't mind this name. We're OK with 'wireless' access to Internet, although it's pretty clear that the packets will hit a wire at some point. Wireless means I'm not pulling a cord along with my phone. 'serverless' similarly means my code is not listening on a socket, although the request does come from some socket, of course
There is still a server, otherwise how do you call your functions from outside ? The most accurate description of "functions as service" is a simple pub sub architecture, some service listens to events, starts a container and execute some script/binary/whatever. In order to send events to the former service, you need a server anyway. Just because it's a different service doesn't make the stack "serverless". Whether it is on Amazon or Azure, you're still paying for the API gateway service. Here is your server.
We are at a point where some dubious marketing hurts development, because that marketing is completely inaccurate and misleading. Every single developer which engages into that misleading marketing should be called out publicly for his bullshit.
I think serverless is a very misleading name, because it does still need server infrastructure and server software. The serverless term will confuse non-technical people to think there's actually no server infrastructure or software needed.
Well, as you posted this after another post that addressed this criticism rather elegantly, I will repeat the relevant bit - " We're OK with 'wireless' access to Internet, although it's pretty clear that the packets will hit a wire at some point. Wireless means I'm not pulling a cord along with my phone. " Non-technical people may assume no server infrastructure. From the developer perspective -this is accurate-; the…
So why not chose a more fitting name?
Earlier quoted context omitted.
Well, as you posted this after another post that addressed this criticism rather elegantly, I will repeat the relevant bit - " We're OK with 'wireless' access to Internet, although it's pretty clear that the packets will hit a wire at some point. Wireless means I'm not pulling a cord along with my phone. " Non-technical people may assume no server infrastructure. From the developer perspective -this is accurate-; the…
The problem with serverless is that it's seems to mean distributed. So why not chose a more fitting name?
And for all those who disagree with "Serverless", come to Serverlessconf London (london.serverlessconf.io) and we can debate it there. In fact, would love to see everyone there!
I think serverless is a very misleading name, because it does still need server infrastructure and server software. The serverless term will confuse non-technical people to think there's actually no server infrastructure or software needed.
Moreover, although function-as-a-service requires hardware to run on (duh), the need for server-grade compute infrastructure is obviated by the short execution times. You could run a FaaS-based offering on a massive array of smartphones.
So sure, if you build a FaaS platform you'll need a scheduler, but you won't need a server, not in the client-server sense and not in the hardware sense either.
So some marketing-oriented people will think that "serverless" is just a buzzword to mean you're not managing the OS & hardware, but there's actually a more positive reading of this term that undermines all the negativity.
Interesting. Will keep an eye on this. And for all those who disagree with "Serverless", come to Serverlessconf London (london.serverlessconf.io) and we can debate it there. In fact, would love to see everyone there!
Nobody disagree with anything but the marketing. "Serveless" is just an inaccurate description of what is actually going on. There is a server otherwise how do you communicate with the outside world? You need an API gateway to your pubsub architecture. Thus calling it "serverless" is misleading. Look we all know, buzzwords and marketing are here to sell, but when marketing is misleading it actually hurts the whole profession, leading to bad choices.