FaaS is an encapsulation of infrastructure

FaaS economics : 

( a few separate discussions )

• - What's the goal of Faas for the vendor? ( A : higher margin )
• - What's the goal for the purchaser? ( A : lower volume )
• - And, if cash is unlimited, what would you use FaaS patterns for? ( I'm mainly in this space of course, as an academic. )

FaaS thus aligns to my research interest about [ self-migrating programs ], which is somewhat biological in consideration. A self-migrating program (c|w)ould carry its memory with it. It just needs fabric to traverse. Traditional idea : virus, and likewise pointers to external memory would also suffice for the preservation of program identity.

FaaS implementations : 

• - fat VMs, like KVM / QEMU ( usually too heavy for FaaS ) 
• - microVMs, like firecracker ( AWS ) 
• - user-space : containers direct to kernel ( primitive FaaS )
• - user-space : kernel sentry, like gvisor ( GCP ) 
• - user-space : app-level VM, like V8 Isolates ( CloudFlare )