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 d0d09f57dc7 Create glossary.en.md (#19551)
d0d09f57dc7 is described below
commit d0d09f57dc7608f1cc2f013233eddf2af5048e6a
Author: Mike0601 <[email protected]>
AuthorDate: Tue Jul 26 14:20:17 2022 +0800
Create glossary.en.md (#19551)
---
docs/document/content/overview/glossary.en.md | 44 +++++++++++++++++++++++++++
1 file changed, 44 insertions(+)
diff --git a/docs/document/content/overview/glossary.en.md
b/docs/document/content/overview/glossary.en.md
new file mode 100644
index 00000000000..dc8898dff9e
--- /dev/null
+++ b/docs/document/content/overview/glossary.en.md
@@ -0,0 +1,44 @@
++++
+pre = "<b>1.2 </b>"
+title = "Core Concepts"
+weight = 2
+chapter = true
++++
+
+## Database Plus
+
+Database Plus is the concept driving Apache ShardingSphere's project
positioning, and it is designed to build a standard layer and ecosystem above
heterogeneous databases. This concept focuses on how to maximize the original
database computing and storage capabilities rather than creating a new
database. Placed above databases, ShardingSphere focuses on enhancing
databases' inter-compatibility and collaboration.
+
+Connect, Enhance, and Pluggable are the core concepts of Database Plus:
+
+### Connect
+
+Through flexible adaptation to the database protocol, SQL dialect, and
database storage, ShardingSphere can quickly connect applications and
multi-model heterogeneous databases.
+
+### Enhance
+
+ShardingSphere can obtain databases' access traffic and provide transparent
enhancement features such as traffic redirection (sharding, read/write
splitting, and shadow DB), transformation (data encryption and masking),
authentication (security, audit, and permission), governance (circuit breaker
and traffic limit) and analysis (QoS and observability).
+
+### Pluggable
+
+The project adopts the micro-kernel and three-layer pluggable model, which
enables the kernel, features, and database ecosystems to be flexibly expanded.
Developers can customize their ShardingSphere just like building with LEGO
blocks.
+
+## Multi Operation Mode
+
+Apache ShardingSphere is a complete set of products applicable to a wide range
of usage scenarios. In addition to the cluster deployment of the production
environment, it also provides corresponding operation modes for engineers in
the development process and automated testing scenarios. Apache ShardingSphere
provides three operation modes: memory mode, standalone mode, and cluster mode.
+
+Source code:
https://github.com/apache/shardingsphere/tree/master/shardingsphere-mode
+
+### Memory mode
+
+Initial configuration or metadata changes caused by SQL execution take effect
only in the current process. Suitable for environment setup of integration
testing, it makes it easy for developers to integrate Apache ShardingSphere in
integrated functional testing without cleaning the running traces. This is the
default mode of Apache ShardingSphere.
+
+### Standalone mode
+
+It can achieve data persistence in terms of metadata information such as data
sources and rules, but it is not able to synchronize metadata to multiple
Apache ShardingSphere instances or be aware of each other in a cluster
environment. Updating metadata through one instance causes inconsistencies in
other instances because they cannot get the latest metadata. It is ideal for
engineers to build a ShardingSphere environment locally.
+
+### Cluster mode
+
+It provides metadata sharing between multiple Apache ShardingSphere instances
and the capability to coordinate states in distributed scenarios. In an actual
production environment for deployment and release, you must use the cluster
mode.
+
+It provides the capabilities necessary for distributed systems, such as
horizontal scaling of computing capability and high availability. Clustered
environments need to store metadata and coordinate nodes' status through a
separately deployed registry center.
