It is big project, we should not include this changes on version 4.x. I plan finishing it at version 5.x. I can start as a branch to do some preparation works now[1].
Hope after finish this project, the landscape of ShardingSphere[2] can be more powerful. [1] https://github.com/apache/incubator-shardingsphere/issues/3691 [2] https://github.com/apache/incubator-shardingsphere/issues/2434 ------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo [email protected] <[email protected]> 于2019年12月9日周一 下午1:29写道： > Hi, ShardingSphere community, > > More and more features are added into ShardingSphere now, as you know, the > scope of ShardingSphere is no longer for sharding only. > There are more and more features related with sharding, such as > distributed transaction, distributed orchestration, observability and so > on; and there are couple of features did not relate with sharding > obviously, for example: encrypt, shadow data source, SQL audit and so on. > > I'd like to discuss about establishing a pluggable platform of > ShardingSphere. The proposal of pluggable platform is decoupling all > features and technical implementations, the benefits are: > > 1. Flexible for add new feature. > 2. Reduce the negative effects if problem occur on one feature. > 3. Provide a platform to make more contributors work together without > interact on each other. > > I plan split all features from sharding-core first, and then use SPI to > introduce features into the pluggable platform(same thing with sharding, > sharding can be remove from main process too). > > The pluggable platform is a blank JDBC and database protocol finally, and > provide assist technical features such as SQL parser and SQL rewrite. > > Any advice? > > ------------------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
