tristaZero commented on issue #6957: URL: https://github.com/apache/shardingsphere/issues/6957#issuecomment-678890846
Hi @gokulsan Sorry for my late response. :-) You are right, `distributed data synchronization` is another unavoidable topic for these distributed database middlewares. Considering the `data consistency`, IMO, there are two issues, i.e., `distributed transaction` for applications and `distributed storage` for there distributed databases themselves. For the first one, `2PC` or `B.A.S.E` distributed transaction solutions are our concerns and developing currently. But concerning the second one, if it is a distributed database `proxy or middleware`, then like MySQL replication between the master node and slave nodes can help a lot. On the other hand, if it is a real `distributed database`, then a distributed storage is supposed to come together accordingly. However, ShardingSphere is more like a distributed database `proxy or middleware ecosystem`. Hence I have to say we did a tradeoff between `data consistency` and `scalability and query efficiency`. Cheers, Trista ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
