Quote from: deanwebb on July 28, 2017, 03:30:18 PM
My guess it's for small companies that are 100% app developers all crammed into a San Francisco townhouse. They don't know about and don't care about VM tech and just want to bang out code for all their unsecure apps to cram into the Apple and Android stores.
BUT... it's going to get marketed to big players that will get taken to the cleaners when the execs *think* they'll be boosting share prices by cutting costs.
I dont think this is the case. There is nothing saying "serverless" has to live in the cloud. Its a way for an application to function. Its not for running your mail server or any other long live server. Its not even something you want to run continuous. I see this as a place to run very specific processes and functions over the course of a session or couple second timeframe then die.
Why have a VM dedicated to this? Hell one step further why go through all the hassle of spinning up a container?
I dont see this as a central repository with a bunch of scripts and repos that are called to run. But Im thinking its more like a python virtualnv spun up segmented off with its own memory/CPU reservation.
Sure I can see there are security concerns. Hell all this stuff came from developers who could give two shits about networking or security. They just want a no-resistance way to build their code and maintain it through out its life-cycle. Just like virtualization, this stuff will mature and become more prod friendly for the masses.