TL;DR: It's just a name. Get over it.
Serverless means no server, which is false, because there is a server that runs your code.
> because the experience of development is such that you don't really have to think about servers, along with all the complexity of provisioning, configuring and managing them.
That sounds like you are talking about 'web hosting' or 'application hosting', which existed decades ago, don't see any point in inventing a confusing buzzword when we have perfectly fine terminologies already.
> TL;DR: It's just a name. Get over it.
It's a useless and confusing marketing buzzword that makes having intelligent conversations harder. I would love to understand your rationale for defending this confusing buzzword.
A marketing buzzword is something like "web scale", which might be used by a non-technical person to describe a technology, but has no real technical meaning. Serverless is not a buzzword because it is the name used for a collection of technologies, even if it isn't a specific product. "Software containers" also falls into this category.
Yes, serverless architectures involve servers. Well done for recognising this, you are very smart. In fact, you are smart enough to realise that the architectures we are talking about here are very distinct from traditional web hosting services. So, it's convenient to use a different name for them.
Finally, it doesn't really matter whether you like the term or not. It is the accepted term and it is here to stay. If you want to engage in conversations on the topic you will need to move past your misgivings.
What collection of technologies does it name? And how is that different from "web scale" technologies that is also a group of technologies?
> Yes, serverless architectures involve servers. Well done for recognising this, you are very smart.
If you would have strong arguments, you wouldn't need snarkiness.
> In fact, you are smart enough to realise that the architectures we are talking about here are very distinct from traditional web hosting services.
That's the exact opposite of what I've said, if you look at it from a server management point of view, traditional web hosting and "serverless" are one and the same, both are used to run the code you upload and both are managed by someone else.
> So, it's convenient to use a different name for them.
It's not convenient, it's confusing.
> Finally, it doesn't really matter whether you like the term or not. It is the accepted term and it is here to stay.
Accepted by who?
> If you want to engage in conversations on the topic you will need to move past your misgivings.
If you want to engage in conversations on any topic with anyone, you should read what's on this website https://yourlogicalfallacyis.com/ and stop doing them.
But didn't we get "The Cloud" to do that? I mean I'm fine with rebranding but this is a really fine line.
I personally am angered at the 'everyone should be a sys admin' culture we've come into as a profession, it completely trivializes the role of sys admins who are critical to any product/company. Good sys admins bring a lot to the table, just like experienced DBAs.
Edit; wow either everyone really hates sys admins and dba's or prefer "adminless", any down voters care to explain?
In truth, I don't think the name 'serverless' will stick in the long term, there is just too much animosity for it. The useage here by AWS is the first time I've seen it in a couple of months. Anecdata, but I think most would admit it's not very common.
I would argue that "sys admins" - in the form of dedicated personnel - are not "critical to an product/company". I know plenty of smaller companies who are successfully bringing in profits, making payroll, etc, but do not have any sysadmins employed. At some point, they will need those skills (and probably stronger DB skills) but these aren't always critical to every project/company/org. Perfect is the enemy of the good.
EDIT: middle ground.
Yeah sure sys admins and dbas aren't critical, but if an organization values what they can do, they can multiply the productivity and effectiveness of the app and product teams.
Specifically, features are faster to implement because the schema is not jacked, the app is responsive and stable because the data is normalizesd and indexed for the access patterns, data is consistent. Customers are happy.
Similar for the network/server side for sys admins.
The policy of "only DBA can make any changes to anything, and all schema changes have to be discussed, reviewed, vetted and approved by DBA" has benefits, in some situations, but also problems.
I had a DBA question why I needed pagination. "No one has ever asked for it before, and never needed it, and I think you're building your application wrong if you need that". After a few weeks of contentious meetings, we got hand-rolled stored procedures for each specific table/query, but they also took days to get to us.
But, hey, you know... at least the tables were normalized and we had "proper" indexes. We just took weeks to get done what should have taken a few hours to prototype (because, during the time we were building the tool, the team we were building it for ended up buying some third party service because we were taking so long).
We've all got war stories of incompetence on all sides (dba, dev, pm, whatever). This is why I advocate "middle ground". I trust a DBA who's actually done a bit of raw coding in their life. I trust a developer who understands the basics of SQL and DB workings (again, 'basics' are fine). I trust the estimates of a PM who is engaged with the team on a regular basis. I trust the views of a business analyst more if they actually show up to meetings and listen to the parties involved.
* how many real or virtual servers are running your code.
* how the servers were provisioned or setup.
* how to access the servers (either via SSH or programmatically), either than through predefined APIs.
* what happens when the servers break.
* what causes the servers to disappear.
* etc.
The "server" concept has been abstracted out of the equation and you're no longer required to think in terms of servers. (there is one exception: RAM usage is still something you need to predict for AWS Lambda.)
Instead, you're thinking in terms of limitations and usage of the service.
With the above said, serverless has a bit of journey to make. The toolchain is growing and the workflow of local development, testing and deployment is still a work in progress. I feel like it's a great time to jump in because there is a lot of exciting work to do and a good foundation to build on top of.
Now the same thing has got another stupid name: Serverless. I wonder what the same stuff will be called two years from now.
What has changed is that the suite of services now exist to fully enable an application to be (almost) completely serverless.
Similar to micro-services, people will overuse the word and it will seem like a fad. IMO, it's more than a fad. Once the toolchain is mature, it will become the default way of building applications.
Web 3.0 is truly serverless because your application lives on a decentralized p2p cloud.
Ethereum/Swarm(or IPFS)/Whisper is an example of a serverless p2p stack.
You may as well call the service they're selling "managed", because that's what it is.
When "cloud" or "serverless" will be cheaper than managing your own dedicated servers, then it will actually be useful. Until then, it's just marketing.
It's akin to someone saying it's "free" because you don't have to think about the money, e.g. you pay with a credit card.
Perhaps the name it should be called is adminless or backend as a service. In any case, there's probably not much one can do about the name at this point.
What's odd is that we already have "infrastructure as a service", which is generally what this is. An entire infrastructure to run your code, without having to set it up (although you still need to configure logging to get useful data in most situations, it seems).
#define TRUE FALSE //Happy debugging
"Serverless" had no previous meaning - it's not like Amazon bastardized an existing term. The word will ultimately be defined once people expect it to mean something specific. Personally I like Amazon's use of the term here.
A recent similar example: the word "performant". The number of stubborn people who screamed "performant isn't a word!" was ridiculous. Everyone understands the intention behind the word "performant" without needing to have it explained to them. The introduction and wide adoption of a word is exactly how new words are folded into language. Language is fluid! Language has never been static and inflexible, and pouting because we have extended the dictionary over and over again for thousands of years is frivolous.
"With serverless computing, your application still runs on servers"
So it's not serverless? Why are you calling it serverless?
This practically fits in the same boat as docker...
It is even specifically incorrect to claim that AWS lambda functions always run on servers; they have at least three distinct execution environments, one of which is IoT devices via AWS Greengrass another being inside the Cloudfront CDN. It's also a stretch to suggest that the primary execution environment for AWS Lambda is a server device; that is not AFAIK specified anywhere.
So, although the term itself may annoy you, the counter-claim that "it must be servers" is a demonstrably false assumption.
Why not call it "hosted" or "virtually-hosted" instead?
A server cannot do anything without being a server.
I quote: "Serverless computing allows you to build and run applications and services without thinking about servers."
Serverless clearly is not serverless.
down voted edit: LOL
If you are paying for servers, your app isn't serverless. Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.