I prefer hold the prefix  `shardingsphere`, 
becaues 
  1. the uniform prefix feels neat .
  2. make people understand the ownership and mean of the module more.
module names that are too long should not be a concern, and it not long


thanks.




------------------ ???????? ------------------
??????:&nbsp;"Haoran Meng"<[email protected]&gt;;
????????:&nbsp;2020??5??15??(??????) ????12:36
??????:&nbsp;"dev"<[email protected]&gt;;

????:&nbsp;Re: Aggregate and redesign modules for ShardingSphere 5.x



Hi, Liang


Point 1 :

I prefer hold the prefix&nbsp; `shardingsphere`,&nbsp; if some moudles name 
with `
shardingsphere` prefix&nbsp; are too long , i suggest&nbsp; may be we can 
consider
optimizing the module name first.

I think without prefix is simpler, but with prefix is more tidy.

Point 2 :

&nbsp;`scaling`&nbsp; is independent ??but it doesn't look like the same level 
as
others.

Thanks!


zhaojun <[email protected]&gt; ??2020??5??15?????? ????10:06??????

&gt; LGTM, it looks jdbc and proxy is light enough after pluggable platform
&gt; complete.
&gt;
&gt; Regards,
&gt; cherrylzhao
&gt; -------------------------------------------------------
&gt; [email protected]
&gt; Jun Zhao(cherrylzhao) Apache ShardingSphere
&gt;
&gt;
&gt; [email protected] <[email protected]&gt; ??2020??5??14?????? 
????10:35??????
&gt;
&gt; &gt; Hi all,
&gt; &gt;
&gt; &gt; Apache ShardingSphere has lots of new features for new version 5.x.
&gt; &gt; It is better to aggregate and redesign modules.
&gt; &gt;
&gt; &gt; The current modules are:
&gt; &gt; ```
&gt; &gt; shardingsphere-spi
&gt; &gt; shardingsphere-sql-parser
&gt; &gt; shardingsphere-database-protocol
&gt; &gt; shardingsphere-underlying
&gt; &gt; sharding-jdbc
&gt; &gt; sharding-proxy
&gt; &gt; sharding-core
&gt; &gt; sharding-spring
&gt; &gt; sharding-orchestration
&gt; &gt; sharding-opentracing
&gt; &gt; sharding-metrics
&gt; &gt; sharding-transaction
&gt; &gt; sharding-scaling
&gt; &gt; master-slave-core
&gt; &gt; encrypt-core
&gt; &gt; shadow-core
&gt; &gt; control-panel
&gt; &gt; shardingsphere-integration-test
&gt; &gt;
&gt; &gt; ```
&gt; &gt;
&gt; &gt; There are serval points need to be adjusted:
&gt; &gt;
&gt; &gt; 1. There are 2 diff prefixes for `shardingsphere` and&nbsp; 
`sharding` we need
&gt; &gt; to unify. `sharding` is a feature name, and `shardingsphere` is too 
long,
&gt; &gt; so I prefer remove all prefixes.
&gt; &gt; 2. We have lots of features and may add more, so it is better to
&gt; aggregate
&gt; &gt; them to a parent modules.
&gt; &gt; 3. The orchestration related modules can be include in control-panel
&gt; &gt; module.
&gt; &gt; 4. It is better to rename shardingsphere-underlying to infra module
&gt; because
&gt; &gt; of it is more shortly and more make sense.
&gt; &gt;
&gt; &gt; So the draft of new modules are:
&gt; &gt;
&gt; &gt; ```
&gt; &gt; spi
&gt; &gt; sql-parser
&gt; &gt; db-protocol
&gt; &gt; infra
&gt; &gt; jdbc
&gt; &gt; proxy
&gt; &gt; spring
&gt; &gt; transaction
&gt; &gt; scaling
&gt; &gt; features
&gt; &gt;&nbsp;&nbsp; -- sharding
&gt; &gt;&nbsp;&nbsp; -- master-slave
&gt; &gt;&nbsp;&nbsp; -- encrypt
&gt; &gt;&nbsp;&nbsp; -- shadow
&gt; &gt; control-panel
&gt; &gt;&nbsp;&nbsp; -- orchestration
&gt; &gt;&nbsp;&nbsp; -- opentracing
&gt; &gt;&nbsp;&nbsp; -- metrics
&gt; &gt; integration-test
&gt; &gt; distribution
&gt; &gt; ```
&gt; &gt;
&gt; &gt; Any suggestion?
&gt; &gt;
&gt; &gt; ------------------
&gt; &gt;
&gt; &gt; Liang Zhang (John)
&gt; &gt; Apache ShardingSphere &amp; Dubbo
&gt; &gt;
&gt;


-- 
Haoran Meng
[email protected]

Reply via email to