Present RSocket to the TOC

[nebhale]

RSocket is an application-layer network protocol designed for micro-services and browser interaction. It is built upon a message-driven, asynchronous, and multiplexed design and embraces "reactive" principals from the Reactive Manifesto. The protocol is transport, payload, programming model, and language agnostic and includes useful features such as flow control and resumability as core concepts. The project is backed by a diverse community of committers and is used at very large scale by some well known companies.

The RSocket team believes that this project aligns well with section 1(c) of the CNCF Charter by standardizing a loosely-coupled communication protocol. We believe that RSocket can benefit not only the projects within the CNCF, but applications that run on top of those projects as well.

By bringing RSocket under the CNCF umbrella, the team hopes to expand the community outside of the Java and C++ strongholds that it currently occupies. By having a neutral host, we hope to foster a larger community interested in contribution and adoption.

Website: http://rsocket.io
GitHub: https://github.com/rsocket
License: Apache License, Version 2.0

[caniszczyk]

Thanks, RFC: @cncf/toc

If I don't hear any objections by Monday, I'll schedule you for 8am PT on Aug 7th or 21st (whatever works best for you)

[bgrant0607]

@caniszczyk I think we need to budget "work time" in the TOC meetings. Maybe we should only do project presentations once a month?

[caniszczyk]

@bgrant0607 that's what I'm going for moving forward, no more than 1 community presentation a meeting unless something is time sensitive

[nebhale]

@caniszczyk We'd prefer August 7, pending any objections.

[justincormack]

It would be nice to have a more detailed comparison with gRPC given the audience, it is briefly mentioned in the FAQ.

[nebhale]

@justincormack We're working on the slides for that now and will be prepared to go into more depth verbally as desired.

[monadic]

@caniszczyk I agree with @bgrant0607 about keeping "work time" free during TOC meetings for now.

[monadic]

Just wanted to say that having spent several hours on this with the principals, I am keen to sponsor RSocket as a sandbox project. The project supports different semantics from gRPC and is perhaps best seen as a distributed rxJava alternative. There are several intriguing properties eg. how flow control may itself be distributed. I have a few concerns, notably that the project may be better suited to being a library within other larger efforts, eg messaging servers, reactive app servers. Also the flow control implementation is credit based which, iirc from amqp, is not free of issues. Nonetheless I am pretty keen to see this become a Sandbox project.

[smaldini]

@monadic it would be interesting to get your opinion separately on the credit based issues. Also if you have comments regarding the Leasing and Resumption specifications, they should ring some bell to you :). Your assessment regarding gRPC is right (It is intended to be a distributed Reactive Streams alternative more than specifically an RxJava one).

[caniszczyk]

scheduled to present on Aug 7th at 8am PT