Thanks Alexis. > Can you please list which ones are notable? The main one seems to be "streaming" replies. Streaming is certainly notable but multiplexing and flow-control are also very important

Jayant Many thanks. Can you please list which ones are notable? The main one seems to be "streaming" replies. This shouldn't prevent someone building a http 1 compatibility layer, if that what helps

gRPC protocol was designed to build high performance, cross platform and usable libraries for building microservices. It was designed on top of HTTP2 to explicitly make use of Full duplex streams to

+1, protocols FTW ;-)

Since you asked the peanut gallery: I would be delighted to see gRPC supersede Thrift and Finangle for a laundry list of reasons. The crux: being burned by Thrift and Finangle's cross-language and

Brandon, Thank-you. It may help if I mention why I raised the question about HTTP 1.x. Overall we are fans of gRPC at Weaveworks. But we stumbled into some issues when trying to use it in this

Given that security spans all the layers and is a complex topic, I'm not sure what we'd add at the current level of detail. Service naming, discovery, load balancing, and routing (service fabric/mesh

YES

Hi, Yaron. This layer diagram is extremely high-level, and the explanations of the levels are intended to be descriptive rather than exhaustive, so it doesn't preclude the service broker model.

On gRPC and HTTP 1.x I think the best way to bring gRPC to the HTTP 1.x world is via OpenAPI (formerly swagger) and JSON, see the blog post here: http://www.grpc.io/blog/coreos We do this in etcd v3:

FYI for awareness, CNCF is also sponsoring FOSDEM this year Begin forwarded message:

Chris, Probably too late to comment, but looking at the charts seems like we are missing a notion of resources binding / dependency, similar to cloud foundry E. G. A web Micro-Service binds to

Sorry, I missed that last call. So apologies if this was discussed. Two thoughts/Questions that come to mind when looking thru the slides: a) Emphasis on security seem to be missing. It

YES

Last week at the CNCF TOC meeting, we discussed issues with the CNCF Reference Architecture and felt it was ready to finalize (and much better than what we had

+Varun and Jayant to answer that

I'd like to understand why gRPC doesn't work with HTTP 1.x

Hi all, "I am not on the TOC, but" I did want to share a few thoughts about GRPC per the call the other day. I was recently at one of those moderated VC dinners where everyone gets put on the spot to

At yesterday's TOC meeting, we discussed formalizing a Fluentd project proposal after having a great experience collaborating with the Fluentd community: https://github.com/cncf/toc/pull/20 For the

Yes