ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 3 independent products, Sharding-JDBC, Sharding-Proxy & Sharding-Sidecar (todo).
ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 2 independent products, Sharding-JDBC & Sharding-Proxy & Sharding-Sidecar (todo).
They all provide functions of data sharding, distributed transaction and database orchestration, applicable in a variety of situations such as Java isomorphism, heterogeneous language and cloud native.
Aiming at reasonably making full use of the computation and storage capacity of database in distributed system, ShardingSphere defines itself as a middleware, rather than a totally new type of database.
As the cornerstone of many enterprises, relational database still takes a huge market share.
Therefore, at current stage, we prefer to focus on its increment instead of a total overturn.
__All available releases are not Apache releases, Apache releases will begin from version 4.0.0__
__Apache releases is beginning from version 4.0.0__
Sharding-Sidecar (TBD) defines itself as a cloud native database agent of Kubernetes or Mesos environment, in charge of all the access to database in the form of DaemonSet.
Through a decentralized and zero-cost solution, it provides a mesh layer interacting with database, i.e., Database Mesh, also referred to as database grid.
Sharding-Sidecar (TODO) defines itself as a cloud native database agent of Kubernetes environment, in charge of all the access to database in the form of sidecar.
It provides a mesh layer interacting with database, we call this as `Database Mesh`.
Database Mesh emphasizes on how to connect distributed database access application with the database.
Focusing on interaction, it effectively organizes the interaction between messy applications and database.
@@ -75,8 +75,8 @@ They are all governed by mesh layer.
| Database | Any | MySQL/PostgreSQL | MySQL/PostgreSQL |
| Connections Cost Number | High | Low | High |
| Heterogeneous Language | Java Only | Any | Any |
| Connections Count Cost | High | Low | High |
| Supported Languages | Java Only | Any | Any |
| Performance | Low loss | Relatively High loss | Low loss |
| Decentralization | Yes | No | No |
| Static Entry | No | Yes | No |
@@ -84,10 +84,10 @@ They are all governed by mesh layer.
### Hybrid Architecture
Sharding-JDBC adopts decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java;
Sharding-Proxy provides static entry and heterogeneous language support, applicable for OLAP application and the sharding databases management and operation situation.
Sharding-Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management and operation situation.
ShardingSphere is an ecosphere consists of multiple endpoints together.
Through mixed use of Sharding-JDBC and Sharding-Proxy and unified sharding strategy by one registry center, ShardingSphere can build application system applicable to all kinds of situations.
Through mixed use of Sharding-JDBC and Sharding-Proxy and unified sharding strategy by same registry center, ShardingSphere can build application system applicable to all kinds of scenarios.
Architects can adjust the system architecture to the most applicable one to current business more freely.
