incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available
Date Sun, 21 Apr 2019 10:52:33 GMT
Hi all,

Apache ShardingSphere (incubating) Team is glad to announce the first
release of Apache ShardingSphere Incubating 4.0.0-RC1.

ShardingSphere is an open-source ecosystem consisted of a set of
distributed database middleware solutions, including 2 independent
products, Sharding-JDBC & Sharding-Proxy.
They both provide functions of data sharding, distributed transaction and
database orchestration, applicable in a variety of situations such as Java
isomorphism, heterogeneous language.
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.

Sharding-JDBC defines itself as a lightweight Java framework that provides
extra service at Java JDBC layer.
With client end connecting directly to the database, it provides service in
the form of jar and requires no extra deployment and dependence.
It can be considered as an enhanced JDBC driver, which is fully compatible
with JDBC and all kinds of ORM frameworks.

* Applicable in any ORM framework based on Java, such as JPA, Hibernate,
Mybatis, Spring JDBC Template or direct use of JDBC.
* Based on any third-party database connection pool, such as DBCP, C3P0,
BoneCP, Druid, HikariCP.
* Support any kind of database that conforms to JDBC standard: MySQL,
Oracle, SQLServer and PostgreSQL for now.

Sharding-Proxy defines itself as a transparent database proxy, providing a
database server that encapsulates database binary protocol to support
heterogeneous languages.
Friendlier to DBA, the MySQL/PostgreSQL version provided now can use any
kind of client access (such as MySQL Command Client, MySQL Workbench,
Navicat etc.) that is compatible of MySQL/PostgreSQL protocol to operate

* Totally transparent to applications, it can be used directly as MySQL and

* Applicable to any kind of compatible of client end that is compatible of
MySQL and PostgreSQL protocol.

Vote Thread:

Download Links:

Release Notes:


ShardingSphere Resources:

- Issue:
- Mailing list:
- Documents:


Liang Zhang (John)
Apache ShardingSphere & Dubbo

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message