This is an automated email from the ASF dual-hosted git repository.
menghaoran 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 fde2649 Update _index.en.md (#12262)
fde2649 is described below
commit fde26496eaf39d313e10ce9a6675999e297cdce1
Author: y2so <[email protected]>
AuthorDate: Tue Sep 7 17:09:41 2021 +0800
Update _index.en.md (#12262)
Slightly edited the content + fixed the English + added Slack
---
docs/document/content/overview/_index.en.md | 42 ++++++++++++++---------------
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/docs/document/content/overview/_index.en.md
b/docs/document/content/overview/_index.en.md
index 84fee2e..e04ba28 100644
--- a/docs/document/content/overview/_index.en.md
+++ b/docs/document/content/overview/_index.en.md
@@ -10,28 +10,28 @@ chapter = true
[](https://github.com/apache/shardingsphere/fork)
[](https://github.com/apache/shardingsphere/watchers)
-**Stargazers over time**
+**Stargazers Over Time**
-[](https://starchart.cc/apache/shardingsphere)
+[](https://starchart.cc/apache/shardingsphere)
-**Contributor over time**
+**Contributors Over Time**
-[](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=apache/shardingsphere)
+[](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=apache/shardingsphere)
-Apache ShardingSphere is an open-source ecosystem consisting of a set of
distributed database solutions, including 3 independent products, JDBC, Proxy &
Sidecar (Planning).
+Apache ShardingSphere is an Open Source ecosystem consisting 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.
-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 aims at reasonably making full use of the computational
and storage capacity of existing databases in a distributed system, rather than
establishing a new database.
+As the cornerstone of enterprises, the relational database has a huge market
share.
+Therefore, we prefer to focus on its incrementation instead of a total
overturn.
-Apache ShardingSphere begin 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 ShardingSphere systems just like building LEGO
blocks. There are lots of SPI extensions for Apache ShardingSphere now and they
are increasing continuously.
+Apache ShardingSphere began to focus on pluggable architecture from version
5.x, and features can be embedded into project flexibility.
+Currently, features such as data sharding, replica query, data encryption,
shadow testing, 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 with
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.
-Welcome communicate with community via [mail
list](mailto:[email protected]).
+Welcome to interact with community via the official [mail
list](mailto:[email protected]) and the [ShardingSphere
Slack](https://app.slack.com/client/T026JKU2DPF/C026MLH7F34).
[](https://www.apache.org/licenses/LICENSE-2.0.html)
[](https://gitter.im/shardingsphere/Lobby)
@@ -56,8 +56,8 @@ With the client end connecting directly to the database, it
provides services in
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.
-* Support any third-party database connection pool, such as DBCP, C3P0,
BoneCP, Druid, HikariCP.
-* Support any kind of JDBC standard database: MySQL, Oracle, SQLServer,
PostgreSQL and any SQL92 followed databases.
+* Supports any third-party database connection pool, such as DBCP, C3P0,
BoneCP, Druid, HikariCP.
+* Supports any kind of JDBC standard database: MySQL, Oracle, SQLServer,
PostgreSQL and any SQL92 followed databases.
@@ -67,16 +67,16 @@ It can be considered as an enhanced JDBC driver, which is
fully compatible with
[](https://store.docker.com/community/images/apache/sharding-proxy)
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 MySQL version provided now can use any kind of terminal
(such as MySQL Command Client, MySQL Workbench, etc.) that is compatible of
MySQL protocol to operate data.
+Friendlier to DBAs, the MySQL version now provided can use any kind of
terminal (such as MySQL Command Client, MySQL Workbench, etc.) that is
compatible of MySQL protocol to operate data.
-* Transparent to applications, it can be used directly as MySQL and PostgreSQL
servers.
+* Transparent towards applications, it can be used directly as MySQL and
PostgreSQL servers.
* Applicable to any kind of terminal 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 a sidecar.
+ShardingSphere-Sidecar (TODO) defines itself as a cloud-native database agent
of the Kubernetes environment, in charge of all database access in the form of
a sidecar.
It provides a mesh layer interacting with the database, we call this `Database
Mesh`.
Database Mesh emphasizes how to connect distributed data-access applications
with the databases.
@@ -97,12 +97,12 @@ They are all governed by the mesh layer.
### Hybrid Architecture
-ShardingSphere-JDBC adopts decentralized architecture, applicable to
high-performance light-weight OLTP application developed with Java;
+ShardingSphere-JDBC adopts a decentralized architecture, applicable to
high-performance light-weight OLTP application developed with Java.
ShardingSphere-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 a mixed use of ShardingSphere-JDBC and ShardingSphere-Proxy and
unified sharding strategy by the same registry center, ShardingSphere can build
an application system applicable to all kinds of scenarios.
-Architects can adjust the system architecture to the most applicable one to
current business more freely.
+ShardingSphere is an ecosystem consisting of multiple endpoints together.
+Through a mixed use of ShardingSphere-JDBC and ShardingSphere-Proxy and a
unified sharding strategy by the same registry center, ShardingSphere can build
an application system that is applicable to all kinds of scenarios.
+Architects can adjust the system architecture to the most applicable one to
their needs to conduct business more freely.
