Hi Community As you know，we has announced the news of Dubbo3.0 several months ago and there are a few of topic mail to discuss this version. Here I would like to come a raw summary some working on it for hearing more advices and talkings about this.
1) Asynchronization (different to 2.7's way) of the Filter chain in the Dubbo Core. The asynchrony of 2.7 is more limited to point-to-point asynchrony (a consumer calls a provider), while the asynchrony of 3.0 focuses on the asynchrony of the whole call chain in width and the programming model of Rx in height. Interestingly, Spring 5.0 released support for Flux and then started addressing asynchrony across processes. 2)Reactive support In recent years, the popularity of the word reactive programming has risen rapidly. Reactive programming is a programming paradigm oriented around data flows and the propagation of change. Dubbo3.0 will realize the rx interface of reactive Stream, so that users can enjoy the response improvement brought by RP and even the architecture upgrade oriented to RP. 3)Exploring the cloud native/ServiceMesh direction The strategy we set is to visit the Envoy community to realize the concept of integrating Dubbo into mesh. At present, the Dubbo agreement has been supported by the Envoy. Of course, Dubbo Mesh is still a long way away from being truly usable. 4)Integration and support Alibaba's internal HSF Dubbo will be the core base of HSF and Dubbo3.0 will learn some good design idea. for a more detailed thinkings and working about Dubbo3.0-preview. We want to write a detailed article for better sharing and discussion among community and hope this article is OK for Dubbo community. Regards Jefflv
