Serverless sometimes refers to something specific and sometimes it's more of an idea or ideology. And that idea is that the server can be completely abstracted away. You don't have to worry about compute capacity, memory management, uptime, cost to some extent.
Serverless sometimes refers to the concept of "functions as a service", basically taking the microservices pattern and realizing "hey, because we're doing things this way, we basically can forget about the server". Somebody is still doing the heavy lifting (AWS, Google Cloud, etc.) but it's now an abstraction and you have limited ability to configure it, and this is fine if you're using it for the right use cases.
It's good to know that folks are starting to solve problems in this way so you can stay in the loop, but avoid going this route to solve problems you don't have.
Thanks, Ben :).Your explanation really came in handy. Serverless is more like No servers but meanwhile, there are actual servers but I'm not dealing with it.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.