2020
DOI: 10.14778/3415478.3415535
|View full text |Cite
|
Sign up to set email alerts
|

TiDB

Abstract: Hybrid Transactional and Analytical Processing (HTAP) databases require processing transactional and analytical queries in isolation to remove the interference between them. To achieve this, it is necessary to maintain different replicas of data specified for the two types of queries. However, it is challenging to provide a consistent view for distributed replicas within a storage system, where analytical requests can efficiently read consistent and fresh data from transactional workloads at scale and with hig… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
38
0
3

Year Published

2021
2021
2023
2023

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 178 publications
(41 citation statements)
references
References 24 publications
0
38
0
3
Order By: Relevance
“…We ran the OLxPBench in different configurations by varying the type and sending rate of workload. In the demonstration, we compare NHtapDB with state-of-the-practice HTAP databases -TiDB [3].…”
Section: Demonstrationmentioning
confidence: 99%
See 1 more Smart Citation
“…We ran the OLxPBench in different configurations by varying the type and sending rate of workload. In the demonstration, we compare NHtapDB with state-of-the-practice HTAP databases -TiDB [3].…”
Section: Demonstrationmentioning
confidence: 99%
“…Using a dual-format store [3,5] will introduce data transfer overhead between the row-based store and column-based store as shown in Figure 1. To keep data fresh, row-based data updates must be propagated to column-based storage as soon as possible.…”
Section: Introductionmentioning
confidence: 99%
“…TiDB (Huang et al, 2020) is an approach to HTAP which uses a row-store DBMS and a columnstore DBMS for OLTP and OLAP workloads respectively. In this approach, multiple row-store DBMS replicas, based on the TiKV distributed DBMS, are deployed as a cluster to handle transactional queries.…”
Section: Related Workmentioning
confidence: 99%
“…Transaction processing (TP) is a key function of a database, which aims to provide atomicity, consistency, isolation, and durability (ACID) features. Most existing cloud-native databases couple TP either with storage layer [27] or with execution layer [42,43]. Coupling TP with Storage Layer.…”
Section: Introductionmentioning
confidence: 99%
“…Some two-layer databases couple TP with the storage layer as shown in Figure 1a. For example, TiDB [27] adopts a distributed transactional key-value (KV) store TiKV [13] as the storage layer, where the TiDB server is the stateless SQL layer that receives SQL requests, performs SQL parsing and optimization, and generates a distributed execution plan. TiKV is responsible for storing shareded data and supports distributed transactions.…”
Section: Introductionmentioning
confidence: 99%