You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by yhs0092 <yh...@163.com> on 2019/12/04 09:57:14 UTC
Fw: [DISCUSSION] Rsocket
This is the content of the mail "[DISCUSSION] Rsocket is hot now" from gylgeek .
There seems some problem with his mailbox : )
Yours sincerely
Yao Haishi
yhs0092@163.com
--------- Forwarded Message ---------
From： gylgeek@gmail.com <gy...@gmail.com>
Date： 12/4/2019 17:50
To： <yh...@163.com>
Subject： [DISCUSSION] Rsocket
RSocket is a binary protocol for use on byte stream transports such as TCP, WebSockets, and Aeron. It enables the following symmetric interaction models via async message passing over a single connection:
request/response (stream of 1)
request/stream (finite stream of many)
fire-and-forget (no response)
event subscription (infinite stream of many)
Learn more at:
http://rsocket.io
https://github.com/rsocket/rsocket-java
Dubbo and SpringCloud already support Rsocket, and take Rsocketas a future development trend.
In spring 5, spring marks asynchronous interfaces such as asyncRestTemplate as @Deprecated , instead to recommend webflux(based on Rsocket).
Dubbo 3.0.0-snapshot also supports responsive programming based on Rsocket.
Reactive should consist of two parts: asynchronous functional programming and streaming programming. But service-comb don't have streaming programming.
Rsocket can also be used in service mesh. Learn more at:
https://www.netifi.com/solutions-servicemesh
Best regards,
Guo YongLiang.
Re: Fw: [DISCUSSION] Rsocket
Posted by Willem Jiang <wi...@gmail.com>.
It sounds good to me. Do we have any proposal for providing the
support of RSocket in ServiceComb Java Chassis?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Dec 6, 2019 at 9:40 AM Liubao (A) <ba...@huawei.com> wrote:
>
> Good. Adding new programming specification for java-chassis is also very important feature. Diving into the topic is welcome.
>
> -----邮件原件-----
> 发件人: YL G [mailto:gylgeek@gmail.com]
> 发送时间: 2019年12月5日 15:33
> 收件人: dev@servicecomb.apache.org
> 主题: Re: Fw: [DISCUSSION] Rsocket
>
> According to my understanding, Rsocket and grpc are very different.
> The main idea of Rsocket is stream.
> In JDK, we can use CompletebleFuture to asynchronous programming.
> When there is only one object like *CompletebleFuture<String>*, it's OK.
> But when we have a List, we would prefer it could like a stream: generate an element and return an element instead of waiting for the whole list done and return like *CompletebleFuture<List>*. To achieve this, the whole system must be built on the stream.
> Rsocket can help at the protocol level. It's not only a protocol, but also provide a new programming specification like *Flux<List>*.
>
> Zheng Feng <zh...@gmail.com> 于 2019年12月4日周三 19:24写道：
>
> > At first glance, it looks like another gPRC but I just find this
> > article [1] to discuss the differences between gRPC and RSocket.
> > I think we need to keep eye on it.
> >
> > [1]
> > https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c95
> > 4e60
> >
> > yhs0092 <yh...@163.com> 于2019年12月4日周三 下午5:57写道：
> >
> > > This is the content of the mail "[DISCUSSION] Rsocket is hot now"
> > > from gylgeek .
> > > There seems some problem with his mailbox : )
> > >
> > >
> > > Yours sincerely
> > >
> > >
> > > Yao Haishi
> > > yhs0092@163.com
> > >
> > >
> > >
> > > --------- Forwarded Message ---------
> > >
> > > From： gylgeek@gmail.com <gy...@gmail.com>
> > > Date： 12/4/2019 17:50
> > > To： <yh...@163.com>
> > > Subject： [DISCUSSION] Rsocket
> > > RSocket is a binary protocol for use on byte stream transports such
> > > as TCP, WebSockets, and Aeron. It enables the following symmetric
> > interaction
> > > models via async message passing over a single connection:
> > >
> > > request/response (stream of 1)
> > > request/stream (finite stream of many) fire-and-forget (no response)
> > > event subscription (infinite stream of many) Learn more at:
> > > http://rsocket.io
> > > https://github.com/rsocket/rsocket-java
> > > Dubbo and SpringCloud already support Rsocket, and take Rsocketas a
> > future
> > > development trend.
> > > In spring 5, spring marks asynchronous interfaces such as
> > > asyncRestTemplate as @Deprecated , instead to recommend
> > > webflux(based on Rsocket).
> > > Dubbo 3.0.0-snapshot also supports responsive programming based on
> > Rsocket.
> > > Reactive should consist of two parts: asynchronous functional
> > > programming and streaming programming. But service-comb don't have
> > > streaming programming.
> > > Rsocket can also be used in service mesh. Learn more at:
> > > https://www.netifi.com/solutions-servicemesh
> > >
> > >
> > > Best regards,
> > > Guo YongLiang.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
答复: Fw: [DISCUSSION] Rsocket
Posted by "Liubao (A)" <ba...@huawei.com>.
Good. Adding new programming specification for java-chassis is also very important feature. Diving into the topic is welcome.
-----邮件原件-----
发件人: YL G [mailto:gylgeek@gmail.com]
发送时间: 2019年12月5日 15:33
收件人: dev@servicecomb.apache.org
主题: Re: Fw: [DISCUSSION] Rsocket
According to my understanding, Rsocket and grpc are very different.
The main idea of Rsocket is stream.
In JDK, we can use CompletebleFuture to asynchronous programming.
When there is only one object like *CompletebleFuture<String>*, it's OK.
But when we have a List, we would prefer it could like a stream: generate an element and return an element instead of waiting for the whole list done and return like *CompletebleFuture<List>*. To achieve this, the whole system must be built on the stream.
Rsocket can help at the protocol level. It's not only a protocol, but also provide a new programming specification like *Flux<List>*.
Zheng Feng <zh...@gmail.com> 于 2019年12月4日周三 19:24写道：
> At first glance, it looks like another gPRC but I just find this
> article [1] to discuss the differences between gRPC and RSocket.
> I think we need to keep eye on it.
>
> [1]
> https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c95
> 4e60
>
> yhs0092 <yh...@163.com> 于2019年12月4日周三 下午5:57写道：
>
> > This is the content of the mail "[DISCUSSION] Rsocket is hot now"
> > from gylgeek .
> > There seems some problem with his mailbox : )
> >
> >
> > Yours sincerely
> >
> >
> > Yao Haishi
> > yhs0092@163.com
> >
> >
> >
> > --------- Forwarded Message ---------
> >
> > From： gylgeek@gmail.com <gy...@gmail.com>
> > Date： 12/4/2019 17:50
> > To： <yh...@163.com>
> > Subject： [DISCUSSION] Rsocket
> > RSocket is a binary protocol for use on byte stream transports such
> > as TCP, WebSockets, and Aeron. It enables the following symmetric
> interaction
> > models via async message passing over a single connection:
> >
> > request/response (stream of 1)
> > request/stream (finite stream of many) fire-and-forget (no response)
> > event subscription (infinite stream of many) Learn more at:
> > http://rsocket.io
> > https://github.com/rsocket/rsocket-java
> > Dubbo and SpringCloud already support Rsocket, and take Rsocketas a
> future
> > development trend.
> > In spring 5, spring marks asynchronous interfaces such as
> > asyncRestTemplate as @Deprecated , instead to recommend
> > webflux(based on Rsocket).
> > Dubbo 3.0.0-snapshot also supports responsive programming based on
> Rsocket.
> > Reactive should consist of two parts: asynchronous functional
> > programming and streaming programming. But service-comb don't have
> > streaming programming.
> > Rsocket can also be used in service mesh. Learn more at:
> > https://www.netifi.com/solutions-servicemesh
> >
> >
> > Best regards,
> > Guo YongLiang.
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Fw: [DISCUSSION] Rsocket
Posted by YL G <gy...@gmail.com>.
According to my understanding, Rsocket and grpc are very different.
The main idea of Rsocket is stream.
In JDK, we can use CompletebleFuture to asynchronous programming.
When there is only one object like *CompletebleFuture<String>*, it's OK.
But when we have a List, we would prefer it could like a stream: generate
an element and return an element instead of waiting for the whole list done
and return like *CompletebleFuture<List>*. To achieve this, the whole
system must be built on the stream.
Rsocket can help at the protocol level. It's not only a protocol, but also
provide a new programming specification like *Flux<List>*.
Zheng Feng <zh...@gmail.com> 于 2019年12月4日周三 19:24写道：
> At first glance, it looks like another gPRC but I just find this article
> [1] to discuss the differences between gRPC and RSocket.
> I think we need to keep eye on it.
>
> [1]
> https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c954e60
>
> yhs0092 <yh...@163.com> 于2019年12月4日周三 下午5:57写道：
>
> > This is the content of the mail "[DISCUSSION] Rsocket is hot now" from
> > gylgeek .
> > There seems some problem with his mailbox : )
> >
> >
> > Yours sincerely
> >
> >
> > Yao Haishi
> > yhs0092@163.com
> >
> >
> >
> > --------- Forwarded Message ---------
> >
> > From： gylgeek@gmail.com <gy...@gmail.com>
> > Date： 12/4/2019 17:50
> > To： <yh...@163.com>
> > Subject： [DISCUSSION] Rsocket
> > RSocket is a binary protocol for use on byte stream transports such as
> > TCP, WebSockets, and Aeron. It enables the following symmetric
> interaction
> > models via async message passing over a single connection:
> >
> > request/response (stream of 1)
> > request/stream (finite stream of many)
> > fire-and-forget (no response)
> > event subscription (infinite stream of many)
> > Learn more at:
> > http://rsocket.io
> > https://github.com/rsocket/rsocket-java
> > Dubbo and SpringCloud already support Rsocket, and take Rsocketas a
> future
> > development trend.
> > In spring 5, spring marks asynchronous interfaces such as
> > asyncRestTemplate as @Deprecated , instead to recommend webflux(based on
> > Rsocket).
> > Dubbo 3.0.0-snapshot also supports responsive programming based on
> Rsocket.
> > Reactive should consist of two parts: asynchronous functional programming
> > and streaming programming. But service-comb don't have streaming
> > programming.
> > Rsocket can also be used in service mesh. Learn more at:
> > https://www.netifi.com/solutions-servicemesh
> >
> >
> > Best regards,
> > Guo YongLiang.
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Fw: [DISCUSSION] Rsocket
Posted by Zheng Feng <zh...@gmail.com>.
At first glance, it looks like another gPRC but I just find this article
[1] to discuss the differences between gRPC and RSocket.
I think we need to keep eye on it.
[1]
https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c954e60
yhs0092 <yh...@163.com> 于2019年12月4日周三 下午5:57写道：
> This is the content of the mail "[DISCUSSION] Rsocket is hot now" from
> gylgeek .
> There seems some problem with his mailbox : )
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0092@163.com
>
>
>
> --------- Forwarded Message ---------
>
> From： gylgeek@gmail.com <gy...@gmail.com>
> Date： 12/4/2019 17:50
> To： <yh...@163.com>
> Subject： [DISCUSSION] Rsocket
> RSocket is a binary protocol for use on byte stream transports such as
> TCP, WebSockets, and Aeron. It enables the following symmetric interaction
> models via async message passing over a single connection:
>
> request/response (stream of 1)
> request/stream (finite stream of many)
> fire-and-forget (no response)
> event subscription (infinite stream of many)
> Learn more at:
> http://rsocket.io
> https://github.com/rsocket/rsocket-java
> Dubbo and SpringCloud already support Rsocket, and take Rsocketas a future
> development trend.
> In spring 5, spring marks asynchronous interfaces such as
> asyncRestTemplate as @Deprecated , instead to recommend webflux(based on
> Rsocket).
> Dubbo 3.0.0-snapshot also supports responsive programming based on Rsocket.
> Reactive should consist of two parts: asynchronous functional programming
> and streaming programming. But service-comb don't have streaming
> programming.
> Rsocket can also be used in service mesh. Learn more at:
> https://www.netifi.com/solutions-servicemesh
>
>
> Best regards,
> Guo YongLiang.
>
>
>
>
>
>
>
>