Skip to content

Commit d88895c

Browse files
committed
overview, media: add TiSpark and update architecture image
Via: pingcap/docs-cn#838, pingcap/docs-cn#850
1 parent 733a5b0 commit d88895c

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

media/tidb-architecture.png

173 KB
Loading

overview.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,12 +55,10 @@ Read the [Roadmap](https://github.com/pingcap/docs/blob/master/ROADMAP.md).
5555

5656
## TiDB architecture
5757

58-
To better understand TiDBs features, you need to understand the TiDB architecture.
58+
To better understand TiDB's features, you need to understand the TiDB architecture. The TiDB cluster includes three key components: the TiDB server, the PD server, and the TiKV server. In addition, TiDB also provides the [TiSpark](https://github.com/pingcap/tispark/) component to satisfy the complex OLAP requirements.
5959

6060
![image alt text](media/tidb-architecture.png)
6161

62-
The TiDB cluster has three components: the TiDB server, the PD server, and the TiKV server.
63-
6462
### TiDB server
6563

6664
The TiDB server is in charge of the following operations:
@@ -93,6 +91,10 @@ As a cluster, PD needs to be deployed to an odd number of nodes. Usually it is r
9391

9492
The TiKV server is responsible for storing data. From an external view, TiKV is a distributed transactional Key-Value storage engine. Region is the basic unit to store data. Each Region stores the data for a particular Key Range which is a left-closed and right-open interval from StartKey to EndKey. There are multiple Regions in each TiKV node. TiKV uses the Raft protocol for replication to ensure the data consistency and disaster recovery. The replicas of the same Region on different nodes compose a Raft Group. The load balancing of the data among different TiKV nodes are scheduled by PD. Region is also the basic unit for scheduling the load balance.
9593

94+
### TiSpark
95+
96+
TiSpark deals with the complex OLAP requirements. TiSpark makes Spark SQL directly run on the storage layer of the TiDB cluster, combines the advantages of the distributed TiKV cluster, and integrates into the big data ecosystem. With TiSpark, TiDB can support both OLTP and OLAP scenarios in one cluster, so the users never need to worry about data synchronization.
97+
9698
## Features
9799

98100
### Horizontal scalability

0 commit comments

Comments
 (0)