Discover and read the best of Twitter Threads about #knative
Most recents (4)
⏰ What time is it? Time for a #Mythbusters thread -- #Serverless edition!
Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!
Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!
1⃣ "Serverless means no servers"
There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.
Myth: BUSTED!
There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.
Myth: BUSTED!
2⃣ "Serverless is cheaper"
Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.
Myth: Kinda BUSTED!
Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.
Myth: Kinda BUSTED!
Join me and @thejaysmith today at GCP Bay Area Group and learn about #Serverless Eventings with @apachekafka and Cloud Run #knative
meetu.ps/e/HYnb2/1GMPZ/a
meetu.ps/e/HYnb2/1GMPZ/a
we're talking about @KnativeProject eventing now 
🚀 Today at #GoogleNext19, we are launching Cloud Run.
Allowing you to run any stateless http container in a fully managed environment, paying only for the exact resources you use. 📦☁️
👉 cloud.google.com/run
Allowing you to run any stateless http container in a fully managed environment, paying only for the exact resources you use. 📦☁️
👉 cloud.google.com/run
😕 Developers love serverless, but feel limited by the available programming languages or the need to rewrite using functions.
👉 Cloud Run brings the properties of serverless to containers: no infra management, fast autoscaling and pay per use.
👉 Cloud Run brings the properties of serverless to containers: no infra management, fast autoscaling and pay per use.
Sometimes, you want more control or have to run on top of Kubernetes, we are also introducing Cloud Run on GKE. Allowing you to run the same serverless workloads with the same developer experience, in your own GKE cluster. cloud.google.com/run/docs/quick…
I wouldn't say that #Knative is overly complex. I'd say that it is early. Even the team says that it is only a 0.1 version. There is a lot to like there. Let me use all the nuance of Twitter to try and put some color on it.
First, the install story is more complex than it should be. YAML files with thousands of lines is huge. Much of that is HTML and such for dashboards. We need to find a better way. This also applies to Istio -- the install has config maps with quoted yaml that has quoted yaml.
Taking a hard dependency on Istio brings a lot of value but adds a lot to the complexity of the system. Installing Istio is complex especially depending on things like mutable admission controllers and auto sidecar injection.
