JiekerTime opened a new issue, #25957: URL: https://github.com/apache/shardingsphere/issues/25957
I learned a lot of sub-table rules, among which the meaning of broadcast table makes me puzzled. What is the meaning of its existence, is it a function of historical legacy？ ---- I guessed some of its benefits, such as disaster tolerance, fast routing, and solving spanning query problems. - about disaster tolerance: When a database or a table goes down, this can lead to data inconsistency or even unavailability of the entire cluster. So this advantage is excluded. - about fast routing Is it really better than single table routing speed? - about solving spanning query problems Most associative queries are merged into the Proxy's memory, and by streaming merge, etc., I don't think this improves performance much, and is a waste of physical storage space. --- I am really troubled and need help to clear the confusion -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
