Stateless serverless platforms like Lambda force a data shipping architecture which hinders any workflows that require state bigger than a webpage like in the i

Stateless serverless platforms like Lambda force a data shipping architecture which hinders any workflows that require state bigger than a webpage like in the included tweet or coordination between function. The functions are short-lived and not reusable, have a limited network bandwidth to S3, and lack P2P communication which does not fit the efficient distributed programming models we know of today. Emerging stateful serverless runtimes[1] have been shown to support even big data applications whilst keeping the scalability and multi-tenancy benefits of FaaS. Combined with scalable fast stores[2][3], I believe we have here the stateful serverless platforms of tomorrow. [1] https://github.com/lsds/faasm https://github.com/lsds/faasm (can run on KNative, includes demos) [2] https://github.com/hydro-project/anna https://github.com/hydro-project/anna (KVS) [3] https://github.com/stanford-mast/pocket https://github.com/stanford-mast/pocket (Multi-tiered storage DRAM+Flash)