Hi I'm hoping that we can dedicate most of tomorrow's call to the Graduation criteria and see if we can't nail them down together. Alexis

+1.

Yes <cncf-toc@...> wrote:

Yes

jayant thanks again for this, which I have now read about N times I think your approach and argument is sound -- but I do agree that getting in front of some users would help greatly. to start with:

+1 Kenneth Owens CTO Cloud Native Platforms Cloud Platforms and Services Group kenowens@... Phone: +1 408 424 0872 Mobile: +1 314 591 5708 Cisco.com Think before you print. This

Thanks very much everyone who pulled this together !

Just a friendly reminder to the wider CNCF community, the Fluentd project proposal is almost ready for a vote: https://github.com/cncf/toc/pull/20 Please make any final comments, I plan on calling for

No argument here, improving the experience for HTTP+JSON is something Google is actively investing in. We see these as complimentary and often entirely overlapping (GRPC is based on HTTP(2) after all)

Thanks, Louis, Disappointingly, it seems like we don't actually disagree on much. I'm guessing that the set of applications where you would choose to use GRPC is much larger than mine, and the set of

Martin, Perhaps your understanding of GRPC is based on the name (I do bemoan this choice from time to time) rather than the feature set and intent. I would encourage you to read

+adding back the grpc folks to comment

Overall it looks good. Just two things that jumped out at me that are missing: 1 - multi-tenancy. I don't think we need to say much, other than its an issue, and while it could appear on several

I'm not personally a fan of RPC, at least for the sort of applications I write. I have lived through several generations of RPC—DCE, Corba, Java RMI, and so on. I'm sure GRPC is the best of the

A global service catalogue is an interesting idea. If it is "like DNS but for cloud native apps" then it presupposes an "HTTP but for cloud native apps". Such as a service broker protocol for

From: Brian Grant [mailto:briangrant@...] Sent: Monday, October 24, 2016 8:18 PM To: Ram, J [Tech] Cc: Chris Aniszczyk; cncf-toc@... Subject: Re: [cncf-toc] [VOTE] End User Reference Architecture

Thanks. And, if you're building a new microservice-based application, you need to use something. What are the choices? an RPC system an open-source REST API framework and OpenAPI codegen for

Fascinating. Thank-you. I shall need at least a day to digest this and respond so please be patient with me :-)

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