Yes, it is a big change for decision. Make new API to 5.x is a good idea. Then we can keep 4.x's API and just do some internal decouple of features and access adaptors (JDBC driver and Database Protocol).
------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo 蒋晓峰 <[email protected]> 于2019年9月29日周日 上午11:21写道： > > > On 2019/09/28 10:14:55, "[email protected]" <[email protected]> > wrote: > > The scope of ShardingSphere keep expanding. Sharding is not the unique > and > > core feature for ShardingSphere anymore. > > > > So we plan to create pluggable infrastructure for database proxy and JDBC > > driver which to let users run it without any additional function, just > > transparent transmission. ShardingSphere can add more features into > `EMPTY` > > infrastructure, such as sharding, master-slave, encrypt, > > distributed-transaction, orchestration and so on. > > > > The API may look like: ShardingDataSource, MasterSlaveDataSource, > > EncryDataSource, DistributedTransactionDataSource and > > OrchestrationDataSource, the yaml and other configuration methods should > > change to this way too. > > > > Every features are independent and can be work together which using > > composited and append-able way. We can provide SSDataSourceFacade to > manage > > how to use them together. > > > > This is one of the reason to why we do not release for 4.0.0 stable > version > > soon, we want more discuss to make decision to change API before 4.0.0 > > stable version release. > > > > Any suggestions? > > > > ------------------ > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > >
