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 f179eeb4314 Update _index.en.md (#19559)
f179eeb4314 is described below
commit f179eeb4314553a90607ee73dfd97dcd909d556c
Author: Mike0601 <[email protected]>
AuthorDate: Tue Jul 26 14:26:42 2022 +0800
Update _index.en.md (#19559)
---
docs/document/content/overview/_index.en.md | 127 +---------------------------
1 file changed, 1 insertion(+), 126 deletions(-)
diff --git a/docs/document/content/overview/_index.en.md
b/docs/document/content/overview/_index.en.md
index 003c25b06a7..386358b3165 100644
--- a/docs/document/content/overview/_index.en.md
+++ b/docs/document/content/overview/_index.en.md
@@ -1,132 +1,7 @@
+++
pre = "<b>1. </b>"
-title = "Overview"
+title = "Project Introduction"
weight = 1
chapter = true
+++
-[](https://github.com/apache/shardingsphere/releases)
-[](https://github.com/apache/shardingsphere/stargazers)
-[](https://github.com/apache/shardingsphere/fork)
-[](https://github.com/apache/shardingsphere/watchers)
-
-**Stargazers Over Time**
-
-[](https://starchart.cc/apache/shardingsphere)
-
-**Contributors Over Time**
-
-[](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=apache/shardingsphere)
-
-Apache ShardingSphere is positioned as a Database Plus, and aims at building a
standard layer and ecosystem above heterogeneous databases.
-It focuses on how to reuse existing databases and their respective upper
layer, rather than creating a new database. The goal is to minimize or
eliminate the challenges caused by underlying databases fragmentation.
-
-The concepts at the core of the project are Connect, Enhance and Pluggable.
-
-- `Connect:` Flexible adaptation of database protocol, SQL dialect and
database storage. It can quickly connect applications and heterogeneous
databases quickly.
-- `Enhance:` Capture database access entry to provide additional features
transparently, such as: redirect (sharding, readwrite-splitting and shadow),
transform (data encrypt and mask), authentication (security, audit and
authority), governance (circuit breaker and access limitation and analyze, QoS
and observability).
-- `Pluggable:` Leveraging the micro kernel and 3 layers pluggable mode,
features and database ecosystem can be embedded flexibily. Developers can
customize their ShardingSphere just like building with LEGO blocks.
-
-ShardingSphere became an [Apache](https://apache.org/index.html#projects-list)
Top-Level Project on April 16, 2020.
-
-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://github.com/apache/shardingsphere/releases)
-
-[](https://twitter.com/ShardingSphere)
-[](https://join.slack.com/t/apacheshardingsphere/shared_invite/zt-sbdde7ie-SjDqo9~I4rYcR18bq0SYTg)
-[](https://gitter.im/shardingsphere/Lobby)
-
-[](https://travis-ci.org/apache/shardingsphere)
-[](https://codecov.io/gh/apache/shardingsphere)
-[](https://snyk.io/test/github/apache/shardingsphere?targetFile=pom.xml)
-[](https://cloud.quality-gate.com/dashboard/branches/30#overview)
-
-[](http://opentracing.io)
-[](https://github.com/apache/skywalking)
-
-
-
-## Introduction
-
-Apache ShardingSphere 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.
-
-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.
-
-### ShardingSphere-JDBC
-
-[](https://mvnrepository.com/artifact/org.apache.shardingsphere/shardingsphere-jdbc)
-
-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;
-* Supports any third-party database connection pool, such as DBCP, C3P0,
BoneCP, HikariCP;
-* Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle,
SQLServer and any JDBC adapted databases.
-
-
-
-### ShardingSphere-Proxy
-
-[](https://nightlies.apache.org/shardingsphere/)
-[](/en/downloads/)
-[](https://hub.docker.com/r/apache/shardingsphere-proxy)
-
-ShardingSphere-Proxy defines itself as a transparent database proxy, providing
a database server that encapsulates database binary protocol to support
heterogeneous languages.
-Currently, MySQL and PostgreSQL (compatible with PostgreSQL-based databases,
such as openGauss) versions are provided.
-It can use any kind of terminal (such as MySQL Command Client, MySQL
Workbench, etc.) that is compatible of MySQL or PostgreSQL protocol to operate
data, which is friendlier to DBAs.
-
-* 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 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.
-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.
-
-
-
-| | *ShardingSphere-JDBC* | *ShardingSphere-Proxy* |
*ShardingSphere-Sidecar* |
-| ----------------------- | --------------------- | ---------------------- |
------------------------ |
-| Database | Any | MySQL/PostgreSQL |
MySQL/PostgreSQL |
-| 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 |
-
-### Hybrid Architecture
-
-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 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.
-
-
-
-## Solution
-
-| *Solutions/Features* | *Distributed Database* | *Data Security* |
*Database Gateway* | *Stress Testing* |
-| -------------------- | ----------------------- | ---------------------|
------------------------------- | ---------------- |
-| | Data Sharding | Data Encrypt |
Heterogeneous Databases Supported | Shadow Database |
-| | Readwrite-splitting | Row Authority (TODO) | SQL
Dialect Translate (TODO) | Observability |
-| | Distributed Transaction | SQL Audit (TODO) |
| |
-| | Elastic Scale-out | SQL Firewall (TODO) |
| |
-| | Highly Available | |
| |
-
-## Roadmap
-
-
