I prefer to think of serverless as: events triggering backend processes without needing a user interface. A very simple example would be receiving emails to a

I prefer to think of serverless as: events triggering backend processes without needing a user interface. A very simple example would be receiving emails to a helpdesk address, extracting pertinent information, looking up the user's priority and their system's details, reformatting the information and posting to a helpdesk system's queue. You have to remember that the term "serverless" is a misnomer, you are using the provider's servers and infrastructure on a pay-as-you-go basis -- with a significant markup. Of course, that markup is the value of you not having to configure, administer, allocate servers, processes, etc on your own. Serverless, like most IT, is well suited to some use-cases and not to others. It takes skill and experience to design the optimal solution for any given requirement.