It's just another buzzword for clueless management to put into plans and reports. This came up in a webcast last year I had with a large SW/HW corporation and even the employees were laughing and there were some quite serious discussions being held about it. In the end the actual developers ignored it as regardless of whether you have the server or someone else hosts it for you, there is still going to be a server there. Management continue to use it...
https://www.ibm.com/blogs/cloud-computing/2016/05/06/serverless-architecture-openwhisk/
IT has been, and always will be, full of buzzwords. But I would not right-off Serverless. It's an additional deployment option and in some instances makes perfect sense. In others, it won't.
An example of how I use it.
My SAAS is listed in AppSource. When some when registers an interest in it Microsoft push their details into an Azure Storage Table that I own. My Azure function is notified that the table changes, reads the data, processes it. Ends.
It's worked flawlessly for months and runs about 15 times a day. Costs a few pence a month to run.
Does it run on a server? Well it runs on a computer somewhere. But I have no idea what flavour it is. It might be Windows, it could be UNIX, it could even be some special ".NET Only Machine" I am not exposed to the server, I don't have responsibility for maintaining it. It might all be running on a single box in one of Microsoft Azure DC's, but its most likely running in some sort of distributed, highly resilient Farm. The sort of infrastructure that not even a major FTSE company can afford. Again, I don't know, and I don't care.
I simply wrote my 25 lines of C# and deployed it.
Compared to the more traditional options it's trivial. I'd have to code my 25 lines as before, but then I'd need more "Fluff" around the side, maybe create a REST API, Hook up the notification handlers etc etc.
Then I'd need to deploy onto a VM, which gives me a hosting cost ( About £11 a month for the cheapest option in Azure ), then I've got a server to worry about .... all for a bit of useful code that runs occasionally.
What took me an around an hour to do could easily have taken a day.