[scrollaway]

It's not either-or. I wouldn't replace "traditional" hosting by Lambda, but among other things it is very suitable for the following use cases:

- You have a mostly static site that needs a couple of dynamic views (eg. comment or payment processing), but the site doesn't get enough traffic to put a webserver behind it.

- You are continuously processing sub-5min tasks and don't want to have to be doing the up/down scaling yourself and you're willing to pay a premium to have the scaling be managed.

- You want an easy way to run a piece of code from various AWS triggers without having to set up webhooks in between.

- Your next employer is a buzzword vulture and you have an idea for a serverless virtual reality blockchain.