Tnx Richard! Nice to see the progress around gRPC. One question: we are currently running all our services as gRPC endpoints in golang on Cloud Run together with Cloud Endpoints (ESPv2) as our Proxy. How could one setup a gRPC Proxyless Service Mesh in the context of Cloud Run?
Hello :) Two questions: 1) is this a new feature or just an explanation of a long-existing feature? 2) If this is a new feature, we can finally deprecate envoy to work with the browser? If both answers are yes, then this is great news!!
xDS is fairly new and significant initiative that gRPC started supporting since v1.30.0 (C++, Java, Go, Python, PHP..) and Node v1.2.0 in 2020. gRPC still actively supports it and brings in new features to xDS, check out the feature list that keeps expanding :) github.com/grpc/grpc/blob/master/doc/grpc_xds_features.md
gRPC xDS does not run on browser, it is mainly for gRPC backend server and client. If you have use cases, request a feature here: github.com/grpc/grpc-web
@@grpcio I use grpc-dart as a backend and in order for my project to be accessible from the browser, I have to use envoy as a proxy server. I figured you'd rolled out a new feature that would save me the trouble of using envoy directly.
Tnx Samuel - this is a really great explanation of ctx One question on the `go SubRequest(subCtx,...)` (time 24:08 of the video) - what happens if the the goroutine carries on after the main `func Request(ctx,...)` served the request? - when the main request is served the `ctx` is cancelled - will this not then initiate a cancel to all of its children, therefore cancelling the `SubRequest` via the `subCtx`?
Great video & slides. Thank you! So this made me wonder - how these contexts propagate to other languages/runtimes - C++/Java/Rust/Python/etc. - Is it some magic behind gRPC or OpenTelemetry (which also has the notion of context), or is something more general missing?
Because of the missing keepalive in Dart i decided to use Websockets for the Messaging and to trigger my grpc api. I wonder if it would be practical to just declare ping and pong protomessages to replace the missing keepalive and send those over long lived streams.
