Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[jun liu]

> And also, there are a lot of sub modules have never been modified almost,
> such as:

Strongly +1 for that. I have found many sub modules increase version number in 
every release cycle while most of them have no content changed.

Best regards,
Jun

> On 16 Aug 2018, at 16:00, Jerrick Zhu  wrote:
> 
> Hi, community
> 
> As you can see, Dubbo now has an ecosystem: https://github.com/dubbo .There
> has a lot of interesting projects there, such as:
> 
> * node, go, python and php implementations
> * dubbo rpc, serialization and registry extensions
> * dubbo samples and dubbo useful plugins and tools
> 
> Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's too
> big. As a result, it takes nearly 30~40mins to finish travis CI.
> 
> And also, there are a lot of sub modules have never been modified almost,
> such as:
> 
> * dubbo-registry-multicast
> * dubbo-registry-redis
> ...
> 
> * dubbo-remoting-grizzly
> * dubbo-remoting-p2p
> * dubbo-remoting-zookeeper
> * dubbo-remoting-mina
> ...
> 
> * dubbo-rpc-injvm
> * dubbo-rpc-memcached
> * dubbo-rpc-redis
> * dubbo-rpc-thrift
> * dubbo-rpc-webservice
> ...
> 
> * dubbo-serialization-fastjson
> * dubbo-serialization-fst
> * dubbo-serialization-jdk
> ...
> 
> So I suggest, move the above sub modules to ecosystem, each of them as a
> single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
> 
> Also, dubbo-demo also needs to move to ecosystem.
> 
> What do u guys think?
> 
> Sincerely.
> 
> Jerrick

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Jerrick Zhu]

On Mon, Aug 20, 2018 at 2:44 PM Zonghai Shang  wrote:

> By the way Dubbo-all.jar should be provided after splitting, which is
>

How do other people think about this?

BTW, this action will be performed on 2.7.x, which is master branch, does
this action needs to be on 2.6.x ?


> convenient for low-level version upgrades.
>
> 凝雨  于2018年8月20日周一 上午10:26写道：
>
> > +1，dubbo It should be streamlined.
> > I agree with keeping the following modules:
> > * dubbo-registry-multicast,
> > * dubbo-rpc-injvm,
> > * dubbo-serialization-fastjson
> > * dubbo-serialization-jdk
> >
> > Huxing Zhang  于2018年8月18日周六 下午2:08写道：
> >
> > > Hi,
> > >
> > > On Fri, Aug 17, 2018 at 5:47 PM Jerrick Zhu 
> wrote:
> > > >
> > > > Another question, do we need to add these sub modules' binary classes
> > to
> > > > dubbo.jar , as the previous hessian-lite module?
> > >
> > > I am supposing this happens to 2.7.x and keep 2.6.x unchanged.
> > > Based on my assumption I think it is unnecessary to do so.
> > >
> > > >
> > > > Or we also remove all of them from dubbo.jar?
> > > >
> > > > On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu 
> > wrote:
> > > >
> > > > > Great. Let's do it. I'll start an issue to track this proposal.
> > > > >
> > > > > On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
> > > > >
> > > > >> +1 Deep agree
> > > > >> --
> > > > >> Best Regards！
> > > > >>
> > > > >> cgfork
> > > > >>
> > > > >> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu 
> > > wrote:
> > > > >> >
> > > > >> > Deep agree with this proposal
> > > > >> > :)
> > > > >> >
> > > > >> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
> > > > >> >
> > > > >> > > I agree with keeping the following modules:
> > > > >> > > * dubbo-registry-multicast,
> > > > >> > > * dubbo-rpc-injvm,
> > > > >> > > * dubbo-serialization-fastjson
> > > > >> > > * dubbo-serialization-jdk
> > >
> > > +1
> > >
> > > > >> > >
> > > > >> > > They're useful for new users and develop experience.
> > > > >> > >
> > > > >> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo 
> > > wrote:
> > > > >> > >
> > > > >> > > > wow, this is a big step but I have somewhat opposite opinion
> > > against
> > > > >> > > > Jerrick's proposal. Instead of keeping recommended
> extensions
> > > only
> > > > >> but
> > > > >> > > > moving out others into eco system, I would like to revise it
> > to
> > > > >> keeping
> > > > >> > > > most used extensions, use Jerrick's list as an example:
> > > > >> > > >
> > > > >> > > > * dubbo-registry-multicast <- should keep, it's good for dev
> > > > >> experience
> > > > >> > > > * dubbo-registry-redis <- should move, since not everyone
> > needs
> > > this
> > > > >> > > > feature
> > > > >> > > > ...
> > > > >> > > >
> > > > >> > > > * dubbo-remoting-grizzly <- should move, ditto
> > > > >> > > > * dubbo-remoting-p2p <- should move, ditto
> > > > >> > > > * dubbo-remoting-zookeeper <- should move, ditto
> > > > >> > > > * dubbo-remoting-mina <- should move, ditto
> > > > >> > > > ...
> > > > >> > > >
> > > > >> > > > * dubbo-rpc-injvm <- should keep, since local-call is one
> > > necessary
> > > > >> > > > feature, think about EJB's local call.
> > > > >> > > > * dubbo-rpc-memcached <- should move
> > > > >> > > > * dubbo-rpc-redis <- should move
> > > > >> > > > * dubbo-rpc-thrift <- should move
> > > > >> > > > * dubbo-rpc-webservice < - should move
> > > > >> > > > ...
> > > > >> > > >
> > > > >> > > > * dubbo-serialization-fastjson <- should keep, very popular
> > json
> > > > >> library
> > > > >> > > > * dubbo-serialization-fst <- should move
> > > > >> > > > * dubbo-serialization-jdk <- should keep, last resort when
> > other
> > > > >> > > > serialization fails to work.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > Just my two cents,
> > > > >> > > > -Ian.
> > > > >> > > >
> > > > >> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu <
> > jerr...@apache.org
> > > >
> > > > >> wrote:
> > > > >> > > >
> > > > >> > > > > Hi, community
> > > > >> > > > >
> > > > >> > > > > As you can see, Dubbo now has an ecosystem:
> > > > >> https://github.com/dubbo
> > > > >> > > > > .There
> > > > >> > > > > has a lot of interesting projects there, such as:
> > > > >> > > > >
> > > > >> > > > > * node, go, python and php implementations
> > > > >> > > > > * dubbo rpc, serialization and registry extensions
> > > > >> > > > > * dubbo samples and dubbo useful plugins and tools
> > > > >> > > > >
> > > > >> > > > > Now Dubbo core which is
> > > http://github.com/apache/incubator-dubbo
> > > > >> ,
> > > > >> > > it's
> > > > >> > > > > too
> > > > >> > > > > big. As a result, it takes nearly 30~40mins to finish
> travis
> > > CI.
> > > > >> > > > >
> > > > >> > > > > And also, there are a lot of sub modules have never been
> > > modified
> > > > >> > > almost,
> > > > >> > > > > such as:
> > > > >> > > > >
> > > > >> > > > > * dubbo-registry-multicast
> > > > >> > > > > * dubbo-registry-redis
> > > > >> > > > > ...
> > > > >> > > > >
> > > > >> > > > > * dubbo-remoting-grizzly
> > > > >> > > > > * dub

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Zonghai Shang]

By the way Dubbo-all.jar should be provided after splitting, which is
convenient for low-level version upgrades.

凝雨  于2018年8月20日周一 上午10:26写道：

> +1，dubbo It should be streamlined.
> I agree with keeping the following modules:
> * dubbo-registry-multicast,
> * dubbo-rpc-injvm,
> * dubbo-serialization-fastjson
> * dubbo-serialization-jdk
>
> Huxing Zhang  于2018年8月18日周六 下午2:08写道：
>
> > Hi,
> >
> > On Fri, Aug 17, 2018 at 5:47 PM Jerrick Zhu  wrote:
> > >
> > > Another question, do we need to add these sub modules' binary classes
> to
> > > dubbo.jar , as the previous hessian-lite module?
> >
> > I am supposing this happens to 2.7.x and keep 2.6.x unchanged.
> > Based on my assumption I think it is unnecessary to do so.
> >
> > >
> > > Or we also remove all of them from dubbo.jar?
> > >
> > > On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu 
> wrote:
> > >
> > > > Great. Let's do it. I'll start an issue to track this proposal.
> > > >
> > > > On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
> > > >
> > > >> +1 Deep agree
> > > >> --
> > > >> Best Regards！
> > > >>
> > > >> cgfork
> > > >>
> > > >> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu 
> > wrote:
> > > >> >
> > > >> > Deep agree with this proposal
> > > >> > :)
> > > >> >
> > > >> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
> > > >> >
> > > >> > > I agree with keeping the following modules:
> > > >> > > * dubbo-registry-multicast,
> > > >> > > * dubbo-rpc-injvm,
> > > >> > > * dubbo-serialization-fastjson
> > > >> > > * dubbo-serialization-jdk
> >
> > +1
> >
> > > >> > >
> > > >> > > They're useful for new users and develop experience.
> > > >> > >
> > > >> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo 
> > wrote:
> > > >> > >
> > > >> > > > wow, this is a big step but I have somewhat opposite opinion
> > against
> > > >> > > > Jerrick's proposal. Instead of keeping recommended extensions
> > only
> > > >> but
> > > >> > > > moving out others into eco system, I would like to revise it
> to
> > > >> keeping
> > > >> > > > most used extensions, use Jerrick's list as an example:
> > > >> > > >
> > > >> > > > * dubbo-registry-multicast <- should keep, it's good for dev
> > > >> experience
> > > >> > > > * dubbo-registry-redis <- should move, since not everyone
> needs
> > this
> > > >> > > > feature
> > > >> > > > ...
> > > >> > > >
> > > >> > > > * dubbo-remoting-grizzly <- should move, ditto
> > > >> > > > * dubbo-remoting-p2p <- should move, ditto
> > > >> > > > * dubbo-remoting-zookeeper <- should move, ditto
> > > >> > > > * dubbo-remoting-mina <- should move, ditto
> > > >> > > > ...
> > > >> > > >
> > > >> > > > * dubbo-rpc-injvm <- should keep, since local-call is one
> > necessary
> > > >> > > > feature, think about EJB's local call.
> > > >> > > > * dubbo-rpc-memcached <- should move
> > > >> > > > * dubbo-rpc-redis <- should move
> > > >> > > > * dubbo-rpc-thrift <- should move
> > > >> > > > * dubbo-rpc-webservice < - should move
> > > >> > > > ...
> > > >> > > >
> > > >> > > > * dubbo-serialization-fastjson <- should keep, very popular
> json
> > > >> library
> > > >> > > > * dubbo-serialization-fst <- should move
> > > >> > > > * dubbo-serialization-jdk <- should keep, last resort when
> other
> > > >> > > > serialization fails to work.
> > > >> > > >
> > > >> > > >
> > > >> > > > Just my two cents,
> > > >> > > > -Ian.
> > > >> > > >
> > > >> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu <
> jerr...@apache.org
> > >
> > > >> wrote:
> > > >> > > >
> > > >> > > > > Hi, community
> > > >> > > > >
> > > >> > > > > As you can see, Dubbo now has an ecosystem:
> > > >> https://github.com/dubbo
> > > >> > > > > .There
> > > >> > > > > has a lot of interesting projects there, such as:
> > > >> > > > >
> > > >> > > > > * node, go, python and php implementations
> > > >> > > > > * dubbo rpc, serialization and registry extensions
> > > >> > > > > * dubbo samples and dubbo useful plugins and tools
> > > >> > > > >
> > > >> > > > > Now Dubbo core which is
> > http://github.com/apache/incubator-dubbo
> > > >> ,
> > > >> > > it's
> > > >> > > > > too
> > > >> > > > > big. As a result, it takes nearly 30~40mins to finish travis
> > CI.
> > > >> > > > >
> > > >> > > > > And also, there are a lot of sub modules have never been
> > modified
> > > >> > > almost,
> > > >> > > > > such as:
> > > >> > > > >
> > > >> > > > > * dubbo-registry-multicast
> > > >> > > > > * dubbo-registry-redis
> > > >> > > > > ...
> > > >> > > > >
> > > >> > > > > * dubbo-remoting-grizzly
> > > >> > > > > * dubbo-remoting-p2p
> > > >> > > > > * dubbo-remoting-zookeeper
> > > >> > > > > * dubbo-remoting-mina
> > > >> > > > > ...
> > > >> > > > >
> > > >> > > > > * dubbo-rpc-injvm
> > > >> > > > > * dubbo-rpc-memcached
> > > >> > > > > * dubbo-rpc-redis
> > > >> > > > > * dubbo-rpc-thrift
> > > >> > > > > * dubbo-rpc-webservice
> > > >> > > > > ...
> > > >> > > > >
> > > >> > > > > * dubbo-serialization-fastjson
> > > >> > > > > * dubbo-serialization-fst
> > > >> > > > > * dubbo-serialization-jdk
> > 

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[凝雨]

+1，dubbo It should be streamlined.
I agree with keeping the following modules:
* dubbo-registry-multicast,
* dubbo-rpc-injvm,
* dubbo-serialization-fastjson
* dubbo-serialization-jdk

Huxing Zhang  于2018年8月18日周六 下午2:08写道：

> Hi,
>
> On Fri, Aug 17, 2018 at 5:47 PM Jerrick Zhu  wrote:
> >
> > Another question, do we need to add these sub modules' binary classes to
> > dubbo.jar , as the previous hessian-lite module?
>
> I am supposing this happens to 2.7.x and keep 2.6.x unchanged.
> Based on my assumption I think it is unnecessary to do so.
>
> >
> > Or we also remove all of them from dubbo.jar?
> >
> > On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu  wrote:
> >
> > > Great. Let's do it. I'll start an issue to track this proposal.
> > >
> > > On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
> > >
> > >> +1 Deep agree
> > >> --
> > >> Best Regards！
> > >>
> > >> cgfork
> > >>
> > >> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu 
> wrote:
> > >> >
> > >> > Deep agree with this proposal
> > >> > :)
> > >> >
> > >> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
> > >> >
> > >> > > I agree with keeping the following modules:
> > >> > > * dubbo-registry-multicast,
> > >> > > * dubbo-rpc-injvm,
> > >> > > * dubbo-serialization-fastjson
> > >> > > * dubbo-serialization-jdk
>
> +1
>
> > >> > >
> > >> > > They're useful for new users and develop experience.
> > >> > >
> > >> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo 
> wrote:
> > >> > >
> > >> > > > wow, this is a big step but I have somewhat opposite opinion
> against
> > >> > > > Jerrick's proposal. Instead of keeping recommended extensions
> only
> > >> but
> > >> > > > moving out others into eco system, I would like to revise it to
> > >> keeping
> > >> > > > most used extensions, use Jerrick's list as an example:
> > >> > > >
> > >> > > > * dubbo-registry-multicast <- should keep, it's good for dev
> > >> experience
> > >> > > > * dubbo-registry-redis <- should move, since not everyone needs
> this
> > >> > > > feature
> > >> > > > ...
> > >> > > >
> > >> > > > * dubbo-remoting-grizzly <- should move, ditto
> > >> > > > * dubbo-remoting-p2p <- should move, ditto
> > >> > > > * dubbo-remoting-zookeeper <- should move, ditto
> > >> > > > * dubbo-remoting-mina <- should move, ditto
> > >> > > > ...
> > >> > > >
> > >> > > > * dubbo-rpc-injvm <- should keep, since local-call is one
> necessary
> > >> > > > feature, think about EJB's local call.
> > >> > > > * dubbo-rpc-memcached <- should move
> > >> > > > * dubbo-rpc-redis <- should move
> > >> > > > * dubbo-rpc-thrift <- should move
> > >> > > > * dubbo-rpc-webservice < - should move
> > >> > > > ...
> > >> > > >
> > >> > > > * dubbo-serialization-fastjson <- should keep, very popular json
> > >> library
> > >> > > > * dubbo-serialization-fst <- should move
> > >> > > > * dubbo-serialization-jdk <- should keep, last resort when other
> > >> > > > serialization fails to work.
> > >> > > >
> > >> > > >
> > >> > > > Just my two cents,
> > >> > > > -Ian.
> > >> > > >
> > >> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  >
> > >> wrote:
> > >> > > >
> > >> > > > > Hi, community
> > >> > > > >
> > >> > > > > As you can see, Dubbo now has an ecosystem:
> > >> https://github.com/dubbo
> > >> > > > > .There
> > >> > > > > has a lot of interesting projects there, such as:
> > >> > > > >
> > >> > > > > * node, go, python and php implementations
> > >> > > > > * dubbo rpc, serialization and registry extensions
> > >> > > > > * dubbo samples and dubbo useful plugins and tools
> > >> > > > >
> > >> > > > > Now Dubbo core which is
> http://github.com/apache/incubator-dubbo
> > >> ,
> > >> > > it's
> > >> > > > > too
> > >> > > > > big. As a result, it takes nearly 30~40mins to finish travis
> CI.
> > >> > > > >
> > >> > > > > And also, there are a lot of sub modules have never been
> modified
> > >> > > almost,
> > >> > > > > such as:
> > >> > > > >
> > >> > > > > * dubbo-registry-multicast
> > >> > > > > * dubbo-registry-redis
> > >> > > > > ...
> > >> > > > >
> > >> > > > > * dubbo-remoting-grizzly
> > >> > > > > * dubbo-remoting-p2p
> > >> > > > > * dubbo-remoting-zookeeper
> > >> > > > > * dubbo-remoting-mina
> > >> > > > > ...
> > >> > > > >
> > >> > > > > * dubbo-rpc-injvm
> > >> > > > > * dubbo-rpc-memcached
> > >> > > > > * dubbo-rpc-redis
> > >> > > > > * dubbo-rpc-thrift
> > >> > > > > * dubbo-rpc-webservice
> > >> > > > > ...
> > >> > > > >
> > >> > > > > * dubbo-serialization-fastjson
> > >> > > > > * dubbo-serialization-fst
> > >> > > > > * dubbo-serialization-jdk
> > >> > > > > ...
> > >> > > > >
> > >> > > > > So I suggest, move the above sub modules to ecosystem, each of
> > >> them as
> > >> > > a
> > >> > > > > single project, such as
> > >> > > https://github.com/dubbo/dubbo-rpc-native-thrift
> > >> > > > >
> > >> > > > > Also, dubbo-demo also needs to move to ecosystem.
> > >> > > > >
> > >> > > > > What do u guys think?
> > >> > > > >
> > >> > > > > Sincerely.
> > >> > > > >
> > >> > > > > Jerrick
> > >> > > > >
> > >> 

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Huxing Zhang]

Hi,

On Fri, Aug 17, 2018 at 5:47 PM Jerrick Zhu  wrote:
>
> Another question, do we need to add these sub modules' binary classes to
> dubbo.jar , as the previous hessian-lite module?

I am supposing this happens to 2.7.x and keep 2.6.x unchanged.
Based on my assumption I think it is unnecessary to do so.

>
> Or we also remove all of them from dubbo.jar?
>
> On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu  wrote:
>
> > Great. Let's do it. I'll start an issue to track this proposal.
> >
> > On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
> >
> >> +1 Deep agree
> >> --
> >> Best Regards！
> >>
> >> cgfork
> >>
> >> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:
> >> >
> >> > Deep agree with this proposal
> >> > :)
> >> >
> >> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
> >> >
> >> > > I agree with keeping the following modules:
> >> > > * dubbo-registry-multicast,
> >> > > * dubbo-rpc-injvm,
> >> > > * dubbo-serialization-fastjson
> >> > > * dubbo-serialization-jdk

+1

> >> > >
> >> > > They're useful for new users and develop experience.
> >> > >
> >> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
> >> > >
> >> > > > wow, this is a big step but I have somewhat opposite opinion against
> >> > > > Jerrick's proposal. Instead of keeping recommended extensions only
> >> but
> >> > > > moving out others into eco system, I would like to revise it to
> >> keeping
> >> > > > most used extensions, use Jerrick's list as an example:
> >> > > >
> >> > > > * dubbo-registry-multicast <- should keep, it's good for dev
> >> experience
> >> > > > * dubbo-registry-redis <- should move, since not everyone needs this
> >> > > > feature
> >> > > > ...
> >> > > >
> >> > > > * dubbo-remoting-grizzly <- should move, ditto
> >> > > > * dubbo-remoting-p2p <- should move, ditto
> >> > > > * dubbo-remoting-zookeeper <- should move, ditto
> >> > > > * dubbo-remoting-mina <- should move, ditto
> >> > > > ...
> >> > > >
> >> > > > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
> >> > > > feature, think about EJB's local call.
> >> > > > * dubbo-rpc-memcached <- should move
> >> > > > * dubbo-rpc-redis <- should move
> >> > > > * dubbo-rpc-thrift <- should move
> >> > > > * dubbo-rpc-webservice < - should move
> >> > > > ...
> >> > > >
> >> > > > * dubbo-serialization-fastjson <- should keep, very popular json
> >> library
> >> > > > * dubbo-serialization-fst <- should move
> >> > > > * dubbo-serialization-jdk <- should keep, last resort when other
> >> > > > serialization fails to work.
> >> > > >
> >> > > >
> >> > > > Just my two cents,
> >> > > > -Ian.
> >> > > >
> >> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu 
> >> wrote:
> >> > > >
> >> > > > > Hi, community
> >> > > > >
> >> > > > > As you can see, Dubbo now has an ecosystem:
> >> https://github.com/dubbo
> >> > > > > .There
> >> > > > > has a lot of interesting projects there, such as:
> >> > > > >
> >> > > > > * node, go, python and php implementations
> >> > > > > * dubbo rpc, serialization and registry extensions
> >> > > > > * dubbo samples and dubbo useful plugins and tools
> >> > > > >
> >> > > > > Now Dubbo core which is http://github.com/apache/incubator-dubbo
> >> ,
> >> > > it's
> >> > > > > too
> >> > > > > big. As a result, it takes nearly 30~40mins to finish travis CI.
> >> > > > >
> >> > > > > And also, there are a lot of sub modules have never been modified
> >> > > almost,
> >> > > > > such as:
> >> > > > >
> >> > > > > * dubbo-registry-multicast
> >> > > > > * dubbo-registry-redis
> >> > > > > ...
> >> > > > >
> >> > > > > * dubbo-remoting-grizzly
> >> > > > > * dubbo-remoting-p2p
> >> > > > > * dubbo-remoting-zookeeper
> >> > > > > * dubbo-remoting-mina
> >> > > > > ...
> >> > > > >
> >> > > > > * dubbo-rpc-injvm
> >> > > > > * dubbo-rpc-memcached
> >> > > > > * dubbo-rpc-redis
> >> > > > > * dubbo-rpc-thrift
> >> > > > > * dubbo-rpc-webservice
> >> > > > > ...
> >> > > > >
> >> > > > > * dubbo-serialization-fastjson
> >> > > > > * dubbo-serialization-fst
> >> > > > > * dubbo-serialization-jdk
> >> > > > > ...
> >> > > > >
> >> > > > > So I suggest, move the above sub modules to ecosystem, each of
> >> them as
> >> > > a
> >> > > > > single project, such as
> >> > > https://github.com/dubbo/dubbo-rpc-native-thrift
> >> > > > >
> >> > > > > Also, dubbo-demo also needs to move to ecosystem.
> >> > > > >
> >> > > > > What do u guys think?
> >> > > > >
> >> > > > > Sincerely.
> >> > > > >
> >> > > > > Jerrick
> >> > > > >
> >> > > >
> >> > >
> >>
> >



-- 
Best Regards！
Huxing

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Jerrick Zhu]

Another question, do we need to add these sub modules' binary classes to
dubbo.jar , as the previous hessian-lite module?

Or we also remove all of them from dubbo.jar?

On Fri, Aug 17, 2018 at 5:36 PM Jerrick Zhu  wrote:

> Great. Let's do it. I'll start an issue to track this proposal.
>
> On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:
>
>> +1 Deep agree
>> --
>> Best Regards！
>>
>> cgfork
>>
>> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:
>> >
>> > Deep agree with this proposal
>> > :)
>> >
>> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
>> >
>> > > I agree with keeping the following modules:
>> > > * dubbo-registry-multicast,
>> > > * dubbo-rpc-injvm,
>> > > * dubbo-serialization-fastjson
>> > > * dubbo-serialization-jdk
>> > >
>> > > They're useful for new users and develop experience.
>> > >
>> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
>> > >
>> > > > wow, this is a big step but I have somewhat opposite opinion against
>> > > > Jerrick's proposal. Instead of keeping recommended extensions only
>> but
>> > > > moving out others into eco system, I would like to revise it to
>> keeping
>> > > > most used extensions, use Jerrick's list as an example:
>> > > >
>> > > > * dubbo-registry-multicast <- should keep, it's good for dev
>> experience
>> > > > * dubbo-registry-redis <- should move, since not everyone needs this
>> > > > feature
>> > > > ...
>> > > >
>> > > > * dubbo-remoting-grizzly <- should move, ditto
>> > > > * dubbo-remoting-p2p <- should move, ditto
>> > > > * dubbo-remoting-zookeeper <- should move, ditto
>> > > > * dubbo-remoting-mina <- should move, ditto
>> > > > ...
>> > > >
>> > > > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
>> > > > feature, think about EJB's local call.
>> > > > * dubbo-rpc-memcached <- should move
>> > > > * dubbo-rpc-redis <- should move
>> > > > * dubbo-rpc-thrift <- should move
>> > > > * dubbo-rpc-webservice < - should move
>> > > > ...
>> > > >
>> > > > * dubbo-serialization-fastjson <- should keep, very popular json
>> library
>> > > > * dubbo-serialization-fst <- should move
>> > > > * dubbo-serialization-jdk <- should keep, last resort when other
>> > > > serialization fails to work.
>> > > >
>> > > >
>> > > > Just my two cents,
>> > > > -Ian.
>> > > >
>> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu 
>> wrote:
>> > > >
>> > > > > Hi, community
>> > > > >
>> > > > > As you can see, Dubbo now has an ecosystem:
>> https://github.com/dubbo
>> > > > > .There
>> > > > > has a lot of interesting projects there, such as:
>> > > > >
>> > > > > * node, go, python and php implementations
>> > > > > * dubbo rpc, serialization and registry extensions
>> > > > > * dubbo samples and dubbo useful plugins and tools
>> > > > >
>> > > > > Now Dubbo core which is http://github.com/apache/incubator-dubbo
>> ,
>> > > it's
>> > > > > too
>> > > > > big. As a result, it takes nearly 30~40mins to finish travis CI.
>> > > > >
>> > > > > And also, there are a lot of sub modules have never been modified
>> > > almost,
>> > > > > such as:
>> > > > >
>> > > > > * dubbo-registry-multicast
>> > > > > * dubbo-registry-redis
>> > > > > ...
>> > > > >
>> > > > > * dubbo-remoting-grizzly
>> > > > > * dubbo-remoting-p2p
>> > > > > * dubbo-remoting-zookeeper
>> > > > > * dubbo-remoting-mina
>> > > > > ...
>> > > > >
>> > > > > * dubbo-rpc-injvm
>> > > > > * dubbo-rpc-memcached
>> > > > > * dubbo-rpc-redis
>> > > > > * dubbo-rpc-thrift
>> > > > > * dubbo-rpc-webservice
>> > > > > ...
>> > > > >
>> > > > > * dubbo-serialization-fastjson
>> > > > > * dubbo-serialization-fst
>> > > > > * dubbo-serialization-jdk
>> > > > > ...
>> > > > >
>> > > > > So I suggest, move the above sub modules to ecosystem, each of
>> them as
>> > > a
>> > > > > single project, such as
>> > > https://github.com/dubbo/dubbo-rpc-native-thrift
>> > > > >
>> > > > > Also, dubbo-demo also needs to move to ecosystem.
>> > > > >
>> > > > > What do u guys think?
>> > > > >
>> > > > > Sincerely.
>> > > > >
>> > > > > Jerrick
>> > > > >
>> > > >
>> > >
>>
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Jerrick Zhu]

Great. Let's do it. I'll start an issue to track this proposal.

On Fri, Aug 17, 2018 at 5:11 PM G C  wrote:

> +1 Deep agree
> --
> Best Regards！
>
> cgfork
>
> On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:
> >
> > Deep agree with this proposal
> > :)
> >
> > Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
> >
> > > I agree with keeping the following modules:
> > > * dubbo-registry-multicast,
> > > * dubbo-rpc-injvm,
> > > * dubbo-serialization-fastjson
> > > * dubbo-serialization-jdk
> > >
> > > They're useful for new users and develop experience.
> > >
> > > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
> > >
> > > > wow, this is a big step but I have somewhat opposite opinion against
> > > > Jerrick's proposal. Instead of keeping recommended extensions only
> but
> > > > moving out others into eco system, I would like to revise it to
> keeping
> > > > most used extensions, use Jerrick's list as an example:
> > > >
> > > > * dubbo-registry-multicast <- should keep, it's good for dev
> experience
> > > > * dubbo-registry-redis <- should move, since not everyone needs this
> > > > feature
> > > > ...
> > > >
> > > > * dubbo-remoting-grizzly <- should move, ditto
> > > > * dubbo-remoting-p2p <- should move, ditto
> > > > * dubbo-remoting-zookeeper <- should move, ditto
> > > > * dubbo-remoting-mina <- should move, ditto
> > > > ...
> > > >
> > > > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
> > > > feature, think about EJB's local call.
> > > > * dubbo-rpc-memcached <- should move
> > > > * dubbo-rpc-redis <- should move
> > > > * dubbo-rpc-thrift <- should move
> > > > * dubbo-rpc-webservice < - should move
> > > > ...
> > > >
> > > > * dubbo-serialization-fastjson <- should keep, very popular json
> library
> > > > * dubbo-serialization-fst <- should move
> > > > * dubbo-serialization-jdk <- should keep, last resort when other
> > > > serialization fails to work.
> > > >
> > > >
> > > > Just my two cents,
> > > > -Ian.
> > > >
> > > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu 
> wrote:
> > > >
> > > > > Hi, community
> > > > >
> > > > > As you can see, Dubbo now has an ecosystem:
> https://github.com/dubbo
> > > > > .There
> > > > > has a lot of interesting projects there, such as:
> > > > >
> > > > > * node, go, python and php implementations
> > > > > * dubbo rpc, serialization and registry extensions
> > > > > * dubbo samples and dubbo useful plugins and tools
> > > > >
> > > > > Now Dubbo core which is http://github.com/apache/incubator-dubbo ,
> > > it's
> > > > > too
> > > > > big. As a result, it takes nearly 30~40mins to finish travis CI.
> > > > >
> > > > > And also, there are a lot of sub modules have never been modified
> > > almost,
> > > > > such as:
> > > > >
> > > > > * dubbo-registry-multicast
> > > > > * dubbo-registry-redis
> > > > > ...
> > > > >
> > > > > * dubbo-remoting-grizzly
> > > > > * dubbo-remoting-p2p
> > > > > * dubbo-remoting-zookeeper
> > > > > * dubbo-remoting-mina
> > > > > ...
> > > > >
> > > > > * dubbo-rpc-injvm
> > > > > * dubbo-rpc-memcached
> > > > > * dubbo-rpc-redis
> > > > > * dubbo-rpc-thrift
> > > > > * dubbo-rpc-webservice
> > > > > ...
> > > > >
> > > > > * dubbo-serialization-fastjson
> > > > > * dubbo-serialization-fst
> > > > > * dubbo-serialization-jdk
> > > > > ...
> > > > >
> > > > > So I suggest, move the above sub modules to ecosystem, each of
> them as
> > > a
> > > > > single project, such as
> > > https://github.com/dubbo/dubbo-rpc-native-thrift
> > > > >
> > > > > Also, dubbo-demo also needs to move to ecosystem.
> > > > >
> > > > > What do u guys think?
> > > > >
> > > > > Sincerely.
> > > > >
> > > > > Jerrick
> > > > >
> > > >
> > >
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Tao yokka]

+1
for remove


[https://mail-online.nosdn.127.net/qiyelogo/defaultAvatar.png]
yokka

iyo...@outlook.com

签名由 网易邮箱大师 定制

On 08/17/2018 17:11，G C wrote：
+1 Deep agree
--
Best Regards！

cgfork

On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:

Deep agree with this proposal
:)

Jerrick Zhu  于2018年8月17日周五 下午1:39写道：

I agree with keeping the following modules:
* dubbo-registry-multicast,
* dubbo-rpc-injvm,
* dubbo-serialization-fastjson
* dubbo-serialization-jdk

They're useful for new users and develop experience.

On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:

wow, this is a big step but I have somewhat opposite opinion against
Jerrick's proposal. Instead of keeping recommended extensions only but
moving out others into eco system, I would like to revise it to keeping
most used extensions, use Jerrick's list as an example:

* dubbo-registry-multicast <- should keep, it's good for dev experience
* dubbo-registry-redis <- should move, since not everyone needs this
feature
...

* dubbo-remoting-grizzly <- should move, ditto
* dubbo-remoting-p2p <- should move, ditto
* dubbo-remoting-zookeeper <- should move, ditto
* dubbo-remoting-mina <- should move, ditto
...

* dubbo-rpc-injvm <- should keep, since local-call is one necessary
feature, think about EJB's local call.
* dubbo-rpc-memcached <- should move
* dubbo-rpc-redis <- should move
* dubbo-rpc-thrift <- should move
* dubbo-rpc-webservice < - should move
...

* dubbo-serialization-fastjson <- should keep, very popular json library
* dubbo-serialization-fst <- should move
* dubbo-serialization-jdk <- should keep, last resort when other
serialization fails to work.


Just my two cents,
-Ian.

On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  wrote:

Hi, community

As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
.There
has a lot of interesting projects there, such as:

* node, go, python and php implementations
* dubbo rpc, serialization and registry extensions
* dubbo samples and dubbo useful plugins and tools

Now Dubbo core which is http://github.com/apache/incubator-dubbo ,
it's
too
big. As a result, it takes nearly 30~40mins to finish travis CI.

And also, there are a lot of sub modules have never been modified
almost,
such as:

* dubbo-registry-multicast
* dubbo-registry-redis
...

* dubbo-remoting-grizzly
* dubbo-remoting-p2p
* dubbo-remoting-zookeeper
* dubbo-remoting-mina
...

* dubbo-rpc-injvm
* dubbo-rpc-memcached
* dubbo-rpc-redis
* dubbo-rpc-thrift
* dubbo-rpc-webservice
...

* dubbo-serialization-fastjson
* dubbo-serialization-fst
* dubbo-serialization-jdk
...

So I suggest, move the above sub modules to ecosystem, each of them as
a
single project, such as
https://github.com/dubbo/dubbo-rpc-native-thrift

Also, dubbo-demo also needs to move to ecosystem.

What do u guys think?

Sincerely.

Jerrick

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[G C]

+1 Deep agree
-- 
Best Regards！

cgfork

On Fri, Aug 17, 2018 at 4:53 PM yuhang xiu  wrote:
>
> Deep agree with this proposal
> :)
>
> Jerrick Zhu  于2018年8月17日周五 下午1:39写道：
>
> > I agree with keeping the following modules:
> > * dubbo-registry-multicast,
> > * dubbo-rpc-injvm,
> > * dubbo-serialization-fastjson
> > * dubbo-serialization-jdk
> >
> > They're useful for new users and develop experience.
> >
> > On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
> >
> > > wow, this is a big step but I have somewhat opposite opinion against
> > > Jerrick's proposal. Instead of keeping recommended extensions only but
> > > moving out others into eco system, I would like to revise it to keeping
> > > most used extensions, use Jerrick's list as an example:
> > >
> > > * dubbo-registry-multicast <- should keep, it's good for dev experience
> > > * dubbo-registry-redis <- should move, since not everyone needs this
> > > feature
> > > ...
> > >
> > > * dubbo-remoting-grizzly <- should move, ditto
> > > * dubbo-remoting-p2p <- should move, ditto
> > > * dubbo-remoting-zookeeper <- should move, ditto
> > > * dubbo-remoting-mina <- should move, ditto
> > > ...
> > >
> > > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
> > > feature, think about EJB's local call.
> > > * dubbo-rpc-memcached <- should move
> > > * dubbo-rpc-redis <- should move
> > > * dubbo-rpc-thrift <- should move
> > > * dubbo-rpc-webservice < - should move
> > > ...
> > >
> > > * dubbo-serialization-fastjson <- should keep, very popular json library
> > > * dubbo-serialization-fst <- should move
> > > * dubbo-serialization-jdk <- should keep, last resort when other
> > > serialization fails to work.
> > >
> > >
> > > Just my two cents,
> > > -Ian.
> > >
> > > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  wrote:
> > >
> > > > Hi, community
> > > >
> > > > As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> > > > .There
> > > > has a lot of interesting projects there, such as:
> > > >
> > > > * node, go, python and php implementations
> > > > * dubbo rpc, serialization and registry extensions
> > > > * dubbo samples and dubbo useful plugins and tools
> > > >
> > > > Now Dubbo core which is http://github.com/apache/incubator-dubbo ,
> > it's
> > > > too
> > > > big. As a result, it takes nearly 30~40mins to finish travis CI.
> > > >
> > > > And also, there are a lot of sub modules have never been modified
> > almost,
> > > > such as:
> > > >
> > > > * dubbo-registry-multicast
> > > > * dubbo-registry-redis
> > > > ...
> > > >
> > > > * dubbo-remoting-grizzly
> > > > * dubbo-remoting-p2p
> > > > * dubbo-remoting-zookeeper
> > > > * dubbo-remoting-mina
> > > > ...
> > > >
> > > > * dubbo-rpc-injvm
> > > > * dubbo-rpc-memcached
> > > > * dubbo-rpc-redis
> > > > * dubbo-rpc-thrift
> > > > * dubbo-rpc-webservice
> > > > ...
> > > >
> > > > * dubbo-serialization-fastjson
> > > > * dubbo-serialization-fst
> > > > * dubbo-serialization-jdk
> > > > ...
> > > >
> > > > So I suggest, move the above sub modules to ecosystem, each of them as
> > a
> > > > single project, such as
> > https://github.com/dubbo/dubbo-rpc-native-thrift
> > > >
> > > > Also, dubbo-demo also needs to move to ecosystem.
> > > >
> > > > What do u guys think?
> > > >
> > > > Sincerely.
> > > >
> > > > Jerrick
> > > >
> > >
> >

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[yuhang xiu]

Deep agree with this proposal
:)

Jerrick Zhu  于2018年8月17日周五 下午1:39写道：

> I agree with keeping the following modules:
> * dubbo-registry-multicast,
> * dubbo-rpc-injvm,
> * dubbo-serialization-fastjson
> * dubbo-serialization-jdk
>
> They're useful for new users and develop experience.
>
> On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:
>
> > wow, this is a big step but I have somewhat opposite opinion against
> > Jerrick's proposal. Instead of keeping recommended extensions only but
> > moving out others into eco system, I would like to revise it to keeping
> > most used extensions, use Jerrick's list as an example:
> >
> > * dubbo-registry-multicast <- should keep, it's good for dev experience
> > * dubbo-registry-redis <- should move, since not everyone needs this
> > feature
> > ...
> >
> > * dubbo-remoting-grizzly <- should move, ditto
> > * dubbo-remoting-p2p <- should move, ditto
> > * dubbo-remoting-zookeeper <- should move, ditto
> > * dubbo-remoting-mina <- should move, ditto
> > ...
> >
> > * dubbo-rpc-injvm <- should keep, since local-call is one necessary
> > feature, think about EJB's local call.
> > * dubbo-rpc-memcached <- should move
> > * dubbo-rpc-redis <- should move
> > * dubbo-rpc-thrift <- should move
> > * dubbo-rpc-webservice < - should move
> > ...
> >
> > * dubbo-serialization-fastjson <- should keep, very popular json library
> > * dubbo-serialization-fst <- should move
> > * dubbo-serialization-jdk <- should keep, last resort when other
> > serialization fails to work.
> >
> >
> > Just my two cents,
> > -Ian.
> >
> > On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  wrote:
> >
> > > Hi, community
> > >
> > > As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> > > .There
> > > has a lot of interesting projects there, such as:
> > >
> > > * node, go, python and php implementations
> > > * dubbo rpc, serialization and registry extensions
> > > * dubbo samples and dubbo useful plugins and tools
> > >
> > > Now Dubbo core which is http://github.com/apache/incubator-dubbo ,
> it's
> > > too
> > > big. As a result, it takes nearly 30~40mins to finish travis CI.
> > >
> > > And also, there are a lot of sub modules have never been modified
> almost,
> > > such as:
> > >
> > > * dubbo-registry-multicast
> > > * dubbo-registry-redis
> > > ...
> > >
> > > * dubbo-remoting-grizzly
> > > * dubbo-remoting-p2p
> > > * dubbo-remoting-zookeeper
> > > * dubbo-remoting-mina
> > > ...
> > >
> > > * dubbo-rpc-injvm
> > > * dubbo-rpc-memcached
> > > * dubbo-rpc-redis
> > > * dubbo-rpc-thrift
> > > * dubbo-rpc-webservice
> > > ...
> > >
> > > * dubbo-serialization-fastjson
> > > * dubbo-serialization-fst
> > > * dubbo-serialization-jdk
> > > ...
> > >
> > > So I suggest, move the above sub modules to ecosystem, each of them as
> a
> > > single project, such as
> https://github.com/dubbo/dubbo-rpc-native-thrift
> > >
> > > Also, dubbo-demo also needs to move to ecosystem.
> > >
> > > What do u guys think?
> > >
> > > Sincerely.
> > >
> > > Jerrick
> > >
> >
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Jerrick Zhu]

I agree with keeping the following modules:
* dubbo-registry-multicast,
* dubbo-rpc-injvm,
* dubbo-serialization-fastjson
* dubbo-serialization-jdk

They're useful for new users and develop experience.

On Fri, Aug 17, 2018 at 11:10 AM Ian Luo  wrote:

> wow, this is a big step but I have somewhat opposite opinion against
> Jerrick's proposal. Instead of keeping recommended extensions only but
> moving out others into eco system, I would like to revise it to keeping
> most used extensions, use Jerrick's list as an example:
>
> * dubbo-registry-multicast <- should keep, it's good for dev experience
> * dubbo-registry-redis <- should move, since not everyone needs this
> feature
> ...
>
> * dubbo-remoting-grizzly <- should move, ditto
> * dubbo-remoting-p2p <- should move, ditto
> * dubbo-remoting-zookeeper <- should move, ditto
> * dubbo-remoting-mina <- should move, ditto
> ...
>
> * dubbo-rpc-injvm <- should keep, since local-call is one necessary
> feature, think about EJB's local call.
> * dubbo-rpc-memcached <- should move
> * dubbo-rpc-redis <- should move
> * dubbo-rpc-thrift <- should move
> * dubbo-rpc-webservice < - should move
> ...
>
> * dubbo-serialization-fastjson <- should keep, very popular json library
> * dubbo-serialization-fst <- should move
> * dubbo-serialization-jdk <- should keep, last resort when other
> serialization fails to work.
>
>
> Just my two cents,
> -Ian.
>
> On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  wrote:
>
> > Hi, community
> >
> > As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> > .There
> > has a lot of interesting projects there, such as:
> >
> > * node, go, python and php implementations
> > * dubbo rpc, serialization and registry extensions
> > * dubbo samples and dubbo useful plugins and tools
> >
> > Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
> > too
> > big. As a result, it takes nearly 30~40mins to finish travis CI.
> >
> > And also, there are a lot of sub modules have never been modified almost,
> > such as:
> >
> > * dubbo-registry-multicast
> > * dubbo-registry-redis
> > ...
> >
> > * dubbo-remoting-grizzly
> > * dubbo-remoting-p2p
> > * dubbo-remoting-zookeeper
> > * dubbo-remoting-mina
> > ...
> >
> > * dubbo-rpc-injvm
> > * dubbo-rpc-memcached
> > * dubbo-rpc-redis
> > * dubbo-rpc-thrift
> > * dubbo-rpc-webservice
> > ...
> >
> > * dubbo-serialization-fastjson
> > * dubbo-serialization-fst
> > * dubbo-serialization-jdk
> > ...
> >
> > So I suggest, move the above sub modules to ecosystem, each of them as a
> > single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
> >
> > Also, dubbo-demo also needs to move to ecosystem.
> >
> > What do u guys think?
> >
> > Sincerely.
> >
> > Jerrick
> >
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Ian Luo]

wow, this is a big step but I have somewhat opposite opinion against
Jerrick's proposal. Instead of keeping recommended extensions only but
moving out others into eco system, I would like to revise it to keeping
most used extensions, use Jerrick's list as an example:

* dubbo-registry-multicast <- should keep, it's good for dev experience
* dubbo-registry-redis <- should move, since not everyone needs this feature
...

* dubbo-remoting-grizzly <- should move, ditto
* dubbo-remoting-p2p <- should move, ditto
* dubbo-remoting-zookeeper <- should move, ditto
* dubbo-remoting-mina <- should move, ditto
...

* dubbo-rpc-injvm <- should keep, since local-call is one necessary
feature, think about EJB's local call.
* dubbo-rpc-memcached <- should move
* dubbo-rpc-redis <- should move
* dubbo-rpc-thrift <- should move
* dubbo-rpc-webservice < - should move
...

* dubbo-serialization-fastjson <- should keep, very popular json library
* dubbo-serialization-fst <- should move
* dubbo-serialization-jdk <- should keep, last resort when other
serialization fails to work.


Just my two cents,
-Ian.

On Thu, Aug 16, 2018 at 4:01 PM Jerrick Zhu  wrote:

> Hi, community
>
> As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> .There
> has a lot of interesting projects there, such as:
>
> * node, go, python and php implementations
> * dubbo rpc, serialization and registry extensions
> * dubbo samples and dubbo useful plugins and tools
>
> Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
> too
> big. As a result, it takes nearly 30~40mins to finish travis CI.
>
> And also, there are a lot of sub modules have never been modified almost,
> such as:
>
> * dubbo-registry-multicast
> * dubbo-registry-redis
> ...
>
> * dubbo-remoting-grizzly
> * dubbo-remoting-p2p
> * dubbo-remoting-zookeeper
> * dubbo-remoting-mina
> ...
>
> * dubbo-rpc-injvm
> * dubbo-rpc-memcached
> * dubbo-rpc-redis
> * dubbo-rpc-thrift
> * dubbo-rpc-webservice
> ...
>
> * dubbo-serialization-fastjson
> * dubbo-serialization-fst
> * dubbo-serialization-jdk
> ...
>
> So I suggest, move the above sub modules to ecosystem, each of them as a
> single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
>
> Also, dubbo-demo also needs to move to ecosystem.
>
> What do u guys think?
>
> Sincerely.
>
> Jerrick
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Zonghai Shang]

+1, Looking forward to the dubbo framework after refactored.

Minxuan Zhuang  于2018年8月16日周四 下午5:18写道：

> +1  dubbo ecosystem has more and more components, so dubbo core can keep
> simple and focus
>
> On Thu, Aug 16, 2018 at 4:58 PM wu tianbiao  wrote:
>
> > +1, UT is really time-consuming
> >
> > +1, Dubbo should be modular, like “Extension Loader” maybe very popular.
> >
> >
> >
> > Consider “git submodule”
> >
> >
> >
> > 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用
> >
> >
> >
> > 
> > 发件人: Mercy 
> > 发送时间: Thursday, August 16, 2018 4:28:26 PM
> > 收件人: dev@dubbo.apache.org; Jerrick Zhu
> > 主题: Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx
> > dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem
> >
> > +1,Totally agree, Dubbo should be modular, and some features could be
> > re-used by other projects, like Spring Cloud LoadBalance.
> >
> >
> > Kind regards,
> >
> > Mercy Ma
> >
> >
> > 在 2018/8/16 下午4:00, Jerrick Zhu 写道:
> > > Hi, community
> > >
> > > As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> > .There
> > > has a lot of interesting projects there, such as:
> > >
> > > * node, go, python and php implementations
> > > * dubbo rpc, serialization and registry extensions
> > > * dubbo samples and dubbo useful plugins and tools
> > >
> > > Now Dubbo core which is http://github.com/apache/incubator-dubbo ,
> it's
> > too
> > > big. As a result, it takes nearly 30~40mins to finish travis CI.
> > >
> > > And also, there are a lot of sub modules have never been modified
> almost,
> > > such as:
> > >
> > > * dubbo-registry-multicast
> > > * dubbo-registry-redis
> > > ...
> > >
> > > * dubbo-remoting-grizzly
> > > * dubbo-remoting-p2p
> > > * dubbo-remoting-zookeeper
> > > * dubbo-remoting-mina
> > > ...
> > >
> > > * dubbo-rpc-injvm
> > > * dubbo-rpc-memcached
> > > * dubbo-rpc-redis
> > > * dubbo-rpc-thrift
> > > * dubbo-rpc-webservice
> > > ...
> > >
> > > * dubbo-serialization-fastjson
> > > * dubbo-serialization-fst
> > > * dubbo-serialization-jdk
> > > ...
> > >
> > > So I suggest, move the above sub modules to ecosystem, each of them as
> a
> > > single project, such as
> https://github.com/dubbo/dubbo-rpc-native-thrift
> > >
> > > Also, dubbo-demo also needs to move to ecosystem.
> > >
> > > What do u guys think?
> > >
> > > Sincerely.
> > >
> > > Jerrick
> > >
> >
> >
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Minxuan Zhuang]

+1  dubbo ecosystem has more and more components, so dubbo core can keep
simple and focus

On Thu, Aug 16, 2018 at 4:58 PM wu tianbiao  wrote:

> +1, UT is really time-consuming
>
> +1, Dubbo should be modular, like “Extension Loader” maybe very popular.
>
>
>
> Consider “git submodule”
>
>
>
> 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用
>
>
>
> 
> 发件人: Mercy 
> 发送时间: Thursday, August 16, 2018 4:28:26 PM
> 收件人: dev@dubbo.apache.org; Jerrick Zhu
> 主题: Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx
> dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem
>
> +1,Totally agree, Dubbo should be modular, and some features could be
> re-used by other projects, like Spring Cloud LoadBalance.
>
>
> Kind regards,
>
> Mercy Ma
>
>
> 在 2018/8/16 下午4:00, Jerrick Zhu 写道:
> > Hi, community
> >
> > As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> .There
> > has a lot of interesting projects there, such as:
> >
> > * node, go, python and php implementations
> > * dubbo rpc, serialization and registry extensions
> > * dubbo samples and dubbo useful plugins and tools
> >
> > Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
> too
> > big. As a result, it takes nearly 30~40mins to finish travis CI.
> >
> > And also, there are a lot of sub modules have never been modified almost,
> > such as:
> >
> > * dubbo-registry-multicast
> > * dubbo-registry-redis
> > ...
> >
> > * dubbo-remoting-grizzly
> > * dubbo-remoting-p2p
> > * dubbo-remoting-zookeeper
> > * dubbo-remoting-mina
> > ...
> >
> > * dubbo-rpc-injvm
> > * dubbo-rpc-memcached
> > * dubbo-rpc-redis
> > * dubbo-rpc-thrift
> > * dubbo-rpc-webservice
> > ...
> >
> > * dubbo-serialization-fastjson
> > * dubbo-serialization-fst
> > * dubbo-serialization-jdk
> > ...
> >
> > So I suggest, move the above sub modules to ecosystem, each of them as a
> > single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
> >
> > Also, dubbo-demo also needs to move to ecosystem.
> >
> > What do u guys think?
> >
> > Sincerely.
> >
> > Jerrick
> >
>
>

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Junlan Shuai]

Good idea.

Jerrick Zhu  于2018年8月16日周四 下午4:01写道：

> Hi, community
>
> As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> .There
> has a lot of interesting projects there, such as:
>
> * node, go, python and php implementations
> * dubbo rpc, serialization and registry extensions
> * dubbo samples and dubbo useful plugins and tools
>
> Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
> too
> big. As a result, it takes nearly 30~40mins to finish travis CI.
>
> And also, there are a lot of sub modules have never been modified almost,
> such as:
>
> * dubbo-registry-multicast
> * dubbo-registry-redis
> ...
>
> * dubbo-remoting-grizzly
> * dubbo-remoting-p2p
> * dubbo-remoting-zookeeper
> * dubbo-remoting-mina
> ...
>
> * dubbo-rpc-injvm
> * dubbo-rpc-memcached
> * dubbo-rpc-redis
> * dubbo-rpc-thrift
> * dubbo-rpc-webservice
> ...
>
> * dubbo-serialization-fastjson
> * dubbo-serialization-fst
> * dubbo-serialization-jdk
> ...
>
> So I suggest, move the above sub modules to ecosystem, each of them as a
> single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
>
> Also, dubbo-demo also needs to move to ecosystem.
>
> What do u guys think?
>
> Sincerely.
>
> Jerrick
>


-- 
Shuai Junlan

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Mercy]

+1,Totally agree, Dubbo should be modular, and some features could be 
re-used by other projects, like Spring Cloud LoadBalance.



Kind regards,

Mercy Ma


在 2018/8/16 下午4:00, Jerrick Zhu 写道:

Hi, community

As you can see, Dubbo now has an ecosystem: https://github.com/dubbo .There
has a lot of interesting projects there, such as:

* node, go, python and php implementations
* dubbo rpc, serialization and registry extensions
* dubbo samples and dubbo useful plugins and tools

Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's too
big. As a result, it takes nearly 30~40mins to finish travis CI.

And also, there are a lot of sub modules have never been modified almost,
such as:

* dubbo-registry-multicast
* dubbo-registry-redis
...

* dubbo-remoting-grizzly
* dubbo-remoting-p2p
* dubbo-remoting-zookeeper
* dubbo-remoting-mina
...

* dubbo-rpc-injvm
* dubbo-rpc-memcached
* dubbo-rpc-redis
* dubbo-rpc-thrift
* dubbo-rpc-webservice
...

* dubbo-serialization-fastjson
* dubbo-serialization-fst
* dubbo-serialization-jdk
...

So I suggest, move the above sub modules to ecosystem, each of them as a
single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift

Also, dubbo-demo also needs to move to ecosystem.

What do u guys think?

Sincerely.

Jerrick

Re: Proposal for moving dubbo-rpc-xxx dubbo-serialization-xxx dubbo-remoting-xxx and dubbo-registry-xxx to dubbo ecosystem

[Jerrick Zhu]

Dubbo core only keeps the api and recommended extension. Keep the core
minimum.
On Thu, Aug 16, 2018 at 4:00 PM Jerrick Zhu  wrote:

> Hi, community
>
> As you can see, Dubbo now has an ecosystem: https://github.com/dubbo
> .There has a lot of interesting projects there, such as:
>
> * node, go, python and php implementations
> * dubbo rpc, serialization and registry extensions
> * dubbo samples and dubbo useful plugins and tools
>
> Now Dubbo core which is http://github.com/apache/incubator-dubbo , it's
> too big. As a result, it takes nearly 30~40mins to finish travis CI.
>
> And also, there are a lot of sub modules have never been modified almost,
> such as:
>
> * dubbo-registry-multicast
> * dubbo-registry-redis
> ...
>
> * dubbo-remoting-grizzly
> * dubbo-remoting-p2p
> * dubbo-remoting-zookeeper
> * dubbo-remoting-mina
> ...
>
> * dubbo-rpc-injvm
> * dubbo-rpc-memcached
> * dubbo-rpc-redis
> * dubbo-rpc-thrift
> * dubbo-rpc-webservice
> ...
>
> * dubbo-serialization-fastjson
> * dubbo-serialization-fst
> * dubbo-serialization-jdk
> ...
>
> So I suggest, move the above sub modules to ecosystem, each of them as a
> single project, such as https://github.com/dubbo/dubbo-rpc-native-thrift
>
> Also, dubbo-demo also needs to move to ecosystem.
>
> What do u guys think?
>
> Sincerely.
>
> Jerrick
>