I agree server-less is not technically accurate. That's why I put it in quotes. However, in the spectrum of bare metal server <-> VM server <-> Heroku-like P

I agree server-less is not technically accurate. That's why I put it in quotes. However, in the spectrum of bare metal server <-> VM server <-> Heroku-like PaaS I'd put this architecture to the right of Heroku. I have less to worry about from an Ops perspective than I do running the app on Heroku. On Heroku, I would need to think about and managing one or several processes. With AWS Lambda, there is no concept of a processes exposed to me like Procfiles expose on Heroku. That's nice in many ways but also limiting in many ways. Also, note that I wasn't building this for rock hard and huge scalability production. I was building it to learn and hopefully help others learn about a fairly new way to build a web application.