4 ms·
ahh so you just worry about your business logic, which will be a bunch of 'functions', and knative will take care of routing, deployment, load etc. ?
by gdsdfe 8y ago
ahh so you just worry about your business logic, which will be a bunch of 'functions', and knative will take care of routing, deployment, load etc. ?
- jacques_chester 8y agoI would say that yes, that is a good statement of the vision that the contributors share.
- gdsdfe 8y agoGot it! thank you! It's actually very interesting ...
- mattsoldo 8y agoIt isn't limited to functions. Knative can run containerees, or with a build system take full app code and deploy it as a container.
- gdsdfe 8y agoso it can be anything really ... hmm
- evankanderson 8y agoI think Knative (and the scale to zero in particular) are best suited for request/response or event-delivery workloads. So you wouldn't want to run (for example) memcache or mysql under knative. FaaS and (HTTP application) PaaS are both good matches. I think it's an open question whether a PaaS like Google Dataflow is a good match or not. It will certainly require more planning, but I think it's doable.
- gdsdfe 8y agoYeah but don't forget this is a higher abstraction on top of microservices. I think the big take away here is that if your app falls into the patten of 80% of modern apps (can't remember where is saw that number, don't quote me :) and is split properly you can have all your 'ops' part as configuration.