You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/08/21 04:21:02 UTC

[GitHub] [shardingsphere] tristaZero commented on issue #6957: How can we apply ShardingSphere for Decentralised Databases?

tristaZero commented on issue #6957:
URL: https://github.com/apache/shardingsphere/issues/6957#issuecomment-678029535


   Hi @gokulsan, Thanks for your attention.
   
   Since I am not familiar with `OrbitDB`or `GunDB`, I am not sure whether my explanation is accurate. If I miss something, welcome your comment.
   
   Actually, the main aim of `Apache ShardingSphere` is to make the traditional DBMS like `MySQL`, `PostgreSQL`, `Oracle`, `SQLServer` has the scalability or turn them to `distributed databases`.
   Base on that, my answer is `NO`. Here is my explanation.
   
   1. SQL. I presume that traditional SQLs do not apply to `OrbitDB`or `GunDB`, right?  But SQL is the communication language between clients and ShardingSphere.
   2. Programing language or protocol. There are two products of `ShardingSphere` for you to choose. `ShardingProxy` is like an enhanced `MySQL` or `PostgreSQL` server, then the binary proposal is used for visiting. On the other hand, `ShardingJDBC` is a lightweight JAVA framework, hence JAVA language is required.
   3. I can not catch your thought. AFAIK, `Decentralised Databases` have the scalability or `distributed storage` already, so users do not need to care about `storage capacity` or `query efficiency`. So why do you want to use `ShardingSphere` for `Decentralised Databases`? 


----------------------------------------------------------------
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:
users@infra.apache.org