> The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. These

> The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. These are good things for serverless, which is what the article is about -- runtime state in a serverless application is bad, and fast startup is good. Serverless instances are intended to be interchangeable and ephemeral. You should be able to start new instances and they should be able to do the same work as the existing instances -- that only works well if they are stateless. Any necessary state should be stored in a database or blob store or some other external state management system.