18 ms·
Isn't this all about to be replaced by serverless containers? With FaaS deployments just taking docker containers or building your code into one when you upload
by manigandham 8y ago
Isn't this all about to be replaced by serverless containers? With FaaS deployments just taking docker containers or building your code into one when you upload?
Why the continued work on a one-off runtime and http response spec instead?
- chris_st 8y agoIt's simpler to just write code, rather than have to try to set up a container.
- manigandham 8y ago>> building your code into one when you upload There's already a publish step, so it can be automatic.
- jacques_chester 8y ago> Isn't this all about to be replaced by serverless containers? Maybe soon, maybe later, maybe never. But it makes sense for a company of Google's size to keep working on the current things they have. Otherwise you wind up with an Osborne Effect and/or frustrated customers.
- com2kid 8y agoIf you need to setup some stand alone functions, this is a great way to do it. I run quite a few utility functions like this, they are simple to write and deploy. If all I want is an HTTP endpoint somewhere, I'm actually not sure why I'd want a serverless container when a stand alone .js file does the trick.