Can anyone tell me how to unsubscribe? Thanks in advance. Jason
zhangli...@apache.org <zhangli...@apache.org> 于2023年3月12日周日 15:05写道： > +1. > > Although the pluggable architecture is becoming more and more powerful, its > project scope is also expanding rapidly. > > Database middleware or computing engine is the best practice of > ShardingSphere. > Therefore, the management of database status should not be included in the > scope. > > Let's keep the scope of ShardingSphere as light as possible. > > ------------------ > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere > > > 赵锦超 <zhaojinc...@apache.org> 于2023年3月12日周日 14:59写道： > > > > > > > > > Hi community, > > > > Currently, ShardingSphere database discovery feature provides the > function > > of automatically discovery the master-slave relationship of the database > > and dynamically correct the status of the data source. It supports > > MYSQL、openGauss database type. > > > > We consider remove this feature, beancase the design of db-discovery and > > dynamic readwrite-splitting of ShardingSphere seems unreasonable, > > ShardingSphere readwrite-splitting should kept concise and not should > rely > > master-slave role and read datasource lists of database discovery. > > > > During the actual development and use, we encountered many problems: > > > > - The database discovery does not meet the pluggable architecture of > > ShardingSphere, it needs to pass the constructed rule to > > readwrite-splitting. > > > > - ShardingSphere does not provide database high availability, it relies > on > > three-party high-availability solutions to find master-slave topological > > relationship, there are too many three-party high-availability solutions > > and they are very complicated, so it is a great challenge for the > > ShardingSphere database discovery feature. > > > > - The database discovery function awareness may cause the entire read > > cluster to be unavailable when use ApsaraDB for reading cluster domain > > names. > > > > Therefore, we intend to remove db-discovery feature in ShardingSphere > into > > a separate branch for maintenance to reduce the cost of understanding and > > maintaining the main code. > > > > Please voice your opinions as fully as possible. Thank you. > > > > > > > > > > [1] https://github.com/apache/shardingsphere/issues/24486 > > > > > > > > > > Regards, > > JinChao > > > > > > > > | | > > 赵锦超 > > | > > | > > 13718687...@163.com > > | > > > > > -- Best wishes, Jason Ma
