> > + Define Dubbo ecosystem > Currently Dubbo is big and there are many related repos, some of them don't > have updates for a long time. > It's better to have a clean understanding here. to define what Dubbo can > provide and will continually maintain.
Agree, this becomes a challenge to all of us. I believe a clear roadmap can attract more people to join us to build them better other than dubbo java and dubbo go. At the same moment I am thinking if it is a good idea to move some extension impls out from the main repo, and keep them one separated repo named 'dubbo-extensions' so we can boost the speed from the perspective of both development and build. + Roadmap and release plan > For Dubbo 3.0, when there is a clean picture what it should look like. We > need a roadmap. > And also for each version, exclude bug fixes, what kind of feature will > include and what may include. > This can help users to know what's happening to Dubbo and what's the next > step, so they can make better plans for their own stuff, like version > upgrading. +1. First of all, for this time we need to define a clear target for version 3.0, and summarize it not only in this mailing list, but also post it on GitHub, so that peoples can understand better what dubbo 3.0 is, and I agree it is a good idea to keep posting the update by weekly or monthly so that everyone know how the project proceeds, no matter they involve themselves in the project or not. + Integration with other project/systems > My understanding for Cloud Native, there are many great projects in the > ecosystem. Dubbo is a PRC framework and many of Cloud features can be > implemented with other projects/systems, > maybe we can discuss what project/systems can Dubbo work together with, > maybe for monitoring, service discovery, tracing, router and more. +1, there are two things out of my brain right now with regarding to what we should support for Cloud Native, one is service discovery in K8s, and the second is direct xDS support in order to make Dubbo work better with other sidecar in service mesh. Regards, -Ian. On Fri, Jul 17, 2020 at 1:20 PM YunKun Huang <[email protected]> wrote: > hey, > > Cloud Native friendly sounds good. but how to define it? What dubbo needs > change to achieve this? > > I would like to add more topic for Dubbo 3.0 > > + Define Dubbo ecosystem > Currently Dubbo is big and there are many related repos, some of them don't > have updates for a long time. > It's better to have a clean understanding here. to define what Dubbo can > provide and will continually maintain. > > + Roadmap and release plan > For Dubbo 3.0, when there is a clean picture what it should look like. We > need a roadmap. > And also for each version, exclude bug fixes, what kind of feature will > include and what may include. > This can help users to know what's happening to Dubbo and what's the next > step, so they can make better plans for their own stuff, like version > upgrading. > > + Integration with other project/systems > My understanding for Cloud Native, there are many great projects in the > ecosystem. Dubbo is a PRC framework and many of Cloud features can be > implemented with other projects/systems, > maybe we can discuss what project/systems can Dubbo work together with, > maybe for monitoring, service discovery, tracing, router and more. > > Yunkun > > > On Thu, Jul 16, 2020 at 7:37 PM Jun Liu <[email protected]> wrote: > > > Hi, Folks > > > > I would like to initiate a discussion about Dubbo 3.0. > > > > Recently, I was thinking about the next generation Dubbo, focusing on > > supporting larger-scale cluster with millions of instances, adapting to > > cloud native infrastructures, working with Service Mesh, etc.. I also > > noticed that many developers in the community are also discussing this > > topic on GitHub and other occasions recently. Most users want to make > their > > Dubbo based micro-services Cloud Native, this requires the change of > Dubbo > > framework itself. > > > > In my mind, the key word of Dubbo 3.0 should be Cloud Native, we should > > focus on making a plan to create a more Cloud Native friendly RPC > > framework. Approximately in 2018, the community had a discussion on > > defining Dubbo 3.0, which is mostly restricted the theme of Reactive > > Stream. But today, when talking about Dubbo 3.0 again, i think Reactive > > Stream is still an important topic, but we should think much broader. > > > > I am just trying to give out some of my own thoughts on Dubbo 3.0. Hope > to > > hear more from you. > > > > Jun > > > > >
