You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by zh...@apache.org on 2021/06/25 02:59:00 UTC
[shardingsphere] branch master updated: Update README.md (#11005)
This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 624062b Update README.md (#11005)
624062b is described below
commit 624062b939a39dbe1beff0ee113c11d1b5af87e1
Author: Srishti Guleria <61...@users.noreply.github.com>
AuthorDate: Fri Jun 25 08:28:19 2021 +0530
Update README.md (#11005)
---
README.md | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/README.md b/README.md
index 9d2a16f..d5a297d 100644
--- a/README.md
+++ b/README.md
@@ -30,17 +30,17 @@
## Overview
Apache ShardingSphere is an open-source ecosystem consisted of a set of distributed database solutions, including 3 independent products, JDBC, Proxy & Sidecar (Planning).
-They all provide functions of data scale out, distributed transaction and distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and cloud native.
+They all provide functions of data scale-out, distributed transaction and distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and cloud-native.
-Apache ShardingSphere aiming at reasonably making full use of the computation and storage capacity of existed database in distributed system, rather than a totally new database.
-As the cornerstone of enterprises, relational database still takes a huge market share.
+Apache ShardingSphere aiming at reasonably making full use of the computation and storage capacity of existed database in a distributed system, rather than a new database.
+As the cornerstone of enterprises, the relational database still takes a huge market share.
Therefore, we prefer to focus on its increment instead of a total overturn.
Apache ShardingSphere begins to focus on pluggable architecture from version 5.x, features can be embedded into project flexibility.
-Currently, the features such as data sharding, replica query, data encrypt, shadow test, and SQL dialects / database protocols such as MySQL, PostgreSQL, SQLServer, Oracle supported are all weaved by plugins.
-Developers can customize their own ShardingSphere systems just like building LEGO blocks. There are lots of SPI extensions for Apache ShardingSphere now and they are increasing continuously.
+Currently, the features such as data sharding, replica query, data encrypt, shadow test, and SQL dialects/database protocols such as MySQL, PostgreSQL, SQLServer, Oracle supported are all weaved by plugins.
+Developers can customize their ShardingSphere systems just like building LEGO blocks. There are lots of SPI extensions for Apache ShardingSphere now and they are increasing continuously.
-ShardingSphere became an [Apache](https://apache.org/index.html#projects-list) Top Level Project on April 16, 2020.
+ShardingSphere became an [Apache](https://apache.org/index.html#projects-list) Top-Level Project on April 16, 2020.
You are welcome to communicate with the community via the [mailing list](mailto:dev@shardingsphere.apache.org).
@@ -50,8 +50,8 @@ You are welcome to communicate with the community via the [mailing list](mailto:
[](https://mvnrepository.com/artifact/org.apache.shardingsphere/shardingsphere-jdbc)
-ShardingSphere-JDBC defines itself as a lightweight Java framework that provides extra services at Java JDBC layer.
-With the client end connecting directly to the database, it provides services in the form of jar and requires no extra deployment and dependence.
+ShardingSphere-JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer.
+With the client end connecting directly to the database, it provides services in the form of a 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 JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC.
@@ -68,19 +68,19 @@ It can be considered as an enhanced JDBC driver, which is fully compatible with
ShardingSphere-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 proxy of 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 data.
-* Totally transparent to applications, it can be used directly as MySQL and PostgreSQL server.
+* Transparent to applications, it can be used directly as MySQL and PostgreSQL servers.
* Applicable to any kind of compatible client end that is compatible with MySQL and PostgreSQL protocol.
### ShardingSphere-Sidecar(TODO)
-ShardingSphere-Sidecar (TODO) defines itself as a cloud native database agent of the Kubernetes environment, in charge of all the access to the database in the form of sidecar.
-It provides a mesh layer interacting with the database, we call this as `Database Mesh`.
+ShardingSphere-Sidecar (TODO) defines itself as a cloud-native database agent of the Kubernetes environment, in charge of all the access to the database in the form of a sidecar.
+It provides a mesh layer interacting with the database, we call this `Database Mesh`.
-Database Mesh emphasizes on how to connect distributed data-access applications with the databases.
-Focusing on interaction, it effectively organizes the interaction between messy applications and the databases.
-The applications and databases those use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly.
+Database Mesh emphasizes how to connect distributed data-access applications with the databases.
+Focusing on interaction, it effectively organizes the interaction between messy applications and databases.
+The applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly.
They are all governed by the mesh layer.
@@ -123,7 +123,7 @@ Architects can adjust the system architecture to the most applicable one to curr
### Database Governance
* Distributed Governance
-* Data migration & Scale out
+* Data migration & Scale-out
* Observability(Tracing/Metrics) Supported
* Data Encryption&Decryption
* Shadow Table for Performance Testing