evankanderson

6 ms·

1.
by evankanderson 4y ago
I think the default is "files-off-disk" image serving (hence NFS, etc). This can be replaced by S3 storage, with the URLs remaining the same (or maybe redirected, if you don't want to pay the bandwidth bill twice). Disclaimer
2.
by evankanderson 4y ago
I suspect distributed NFS won't help here when the problem is that a server gets slow / overloaded. In particular, this setup was actually I/O bound and there wasn't more I/O to be had.
3.
by evankanderson 7y ago
Pivotal is also on the steering committee. Representation is based on contributions to the project, and Google has publicly stated that they look forward to not being a majority on the steering committee (when other companies have exceeded
4.
by evankanderson 7y ago
Hi, Knative team member here. What you're describing with injecting outbound proxies is definitely something that Istio does in service mesh mode. When Knative launched 0.1 over a year ago, we had a pretty hard dependency on Istio. We
5.
by evankanderson 7y ago
It depends on the language you're using and how you manage your dependencies. If you're using Java, see this writeup for how different frameworks can affect startup time: https://medium.com/google-cloud/java-f
6.
by evankanderson 7y ago
App Engine is still GA and is still having features added. Disclaimer: I work on both Cloud Run and App Engine at Google.
7.
by evankanderson 7y ago
Cloud Run is a perfectly reasonable choice for hosting websites -- it's a serverless HTTP platform that uses containers as the base packaging and runtime infrastructure. Unlike something like Fargate, it supports automatic scaling of c
8.
by evankanderson 8y ago
Serverless means that you as a developer don't have to manage servers. There's still real computers behind the "serverless". Knative calls the role of the person providing the servers are "operator". Kubernetes
9.
by evankanderson 8y ago
I 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 ar
10.
by evankanderson 8y ago
One of the items that's not present at the moment (and dewitt can probably provide additional color) is the top-level developer shell which puts the pieces together with a minimal amount of client-side work. If you can see Oren's
11.
by evankanderson 8y ago
That looks more like GKE or AKS.
12.
by evankanderson 8y ago
How big is your Kubernetes cluster?
13.
by evankanderson 8y ago
"eventing" is building an ecosystem to make it easy to connect events to event consumers (whether they are Knative Services, k8s services, VMs, or even a SaaS). In order to do this, we've broken the problem down into 3 parts:
14.
by evankanderson 8y ago
This is a way to deploy and manage a stateless web application ("function") without needing to get into a bunch of low-level details, and get closer to pay-for-what-you-use.
15.
by evankanderson 8y ago
See also: https://medium.com/@mchmarny/build-deploy-manage-modern-serv... https://www.ibm.com/blogs/cloud-computing/2018/07/24/ibm-clo... and one by this "Google" thi