Hi community & liang,
For the first point, I have some suggestions. Do you want remove the binary jar file name’s prefixes? I suggest for the binary jar file name, we have a common prefixes. For this, at user’s web application lib directory, about the shardingsphere’ jar file will at a fixed position, it will be convenient for user to check jar file. Otherwise, if the jar files don’t have a common prefixes, They will be not at a fixed position and user must browse the whole directory and find the file. Thanks! Zonglei Dong Apache ShardingSphere On 05/14/2020 22:35，[email protected]<[email protected]> wrote： Hi all, Apache ShardingSphere has lots of new features for new version 5.x. It is better to aggregate and redesign modules. The current modules are: ``` shardingsphere-spi shardingsphere-sql-parser shardingsphere-database-protocol shardingsphere-underlying sharding-jdbc sharding-proxy sharding-core sharding-spring sharding-orchestration sharding-opentracing sharding-metrics sharding-transaction sharding-scaling master-slave-core encrypt-core shadow-core control-panel shardingsphere-integration-test ``` There are serval points need to be adjusted: 1. There are 2 diff prefixes for `shardingsphere` and `sharding` we need to unify. `sharding` is a feature name, and `shardingsphere` is too long, so I prefer remove all prefixes. 2. We have lots of features and may add more, so it is better to aggregate them to a parent modules. 3. The orchestration related modules can be include in control-panel module. 4. It is better to rename shardingsphere-underlying to infra module because of it is more shortly and more make sense. So the draft of new modules are: ``` spi sql-parser db-protocol infra jdbc proxy spring transaction scaling features -- sharding -- master-slave -- encrypt -- shadow control-panel -- orchestration -- opentracing -- metrics integration-test distribution ``` Any suggestion? ------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo
