6 ms·
This is open source, so "someone" has to run it. This someone could be e.g. IBM or RedHat, it could also be someone like Adobe that wants to offer a FaaS integ
by cnj 9y ago
This is open source, so "someone" has to run it.
This someone could be e.g. IBM or RedHat, it could also be someone like Adobe that wants to offer a FaaS integrated into their main product.
It could also be your own company, e.g. you could have an infrastructure team that provides it for all other teams.
- doppel 9y agoI find mentions of “deployments”, but unlike a platform like Kubernetes I can’t seem to find any mention of how to set up the “serverless servers” anywhere. And until then it’s just a really neat local CLI
- masukomi 9y agoyeah that was my take too. I have zero clue what's involved with the hosting of this and as it's an open source serverless product that's the most important bit. How easy or hard it is to use is irrelevant if i don't know _where_ to point things or what to do to make there be something to point things at.
- bri3d 9y agoIt looks like OpenWhisk right now deploys onto JVM application servers you provision yourself, using runc+Docker and Akka clustering under the hood to orchestrate everything. I think they have plans to target Kubernetes as well. FaaS/"serverless" (a terrible name) is just a layer over an orchestration/deployment system (like Kube) that spins up instances in response to triggers / events and handles routing and scheduling of the instances in a way that's supposed to be transparent to the end-user. https://github.com/apache/incubator-openwhisk/blob/master/docs/deploy.md https://github.com/apache/incubator-openwhisk/blob/master/do...