April 25, 2021 – PingCAP, a leading enterprise open source distributed database vendor, has released version 5.0 of TiDB for enterprise core scenarios. TiDB 5.0 has made great progress in terms of performance, stability, and ease of use. It has added a number of enterprise features in terms of transaction Processing, high availability and DISASTER recovery, and security compliance. Large-scale parallel processing (HTAP) architecture becomes a distributed database with full HTAP capabilities, providing a stack of data service platform for high-growth enterprises and digital innovation scenarios.
Since 2020, the digital transformation of enterprises has entered the deep water area, and the digital scene of the industry has exploded. The data shows the trend of mass, real-time and online. As enterprises have higher and higher requirements on real-time and reliability of data, the traditional heterogeneous data stack coordinated by multiple components, such as database, middleware and big data, is exposed to problems such as difficulty in on-line implementation and extremely high maintenance cost, which seriously hinders the process of enterprise digitization.
HTAP (Hybrid Transactional/Analytical Processing) databases can support both online transaction Processing (OLTP) and online Analytical Processing (OLAP) scenarios ona single data source. Avoids the heavy data interaction between online and offline databases in traditional architectures. Gartner believes that HTAP database will become an important development trend in the database field, and an integrated data platform will accelerate the digital transformation.
Distributed database with full HTAP capabilities
As a leading enterprise distributed database product, TiDB implemented OLTP Scale (Scale expansion of online transaction processing) as early as version 1.0, and initial HTAP capabilities have been implemented in version 4.0. Version 5.0 introduces the MPP architecture based on the original HTAP engine TiFlash to provide a distributed computing engine matching storage and further improve the parallel computing and analysis capability under massive data. By sharing the SQL front end with TIDB-Server and realizing the sharing of parsers and optimizers, TiDB provides an integrated entrance to the business, automatically selects standalone execution or MPP mode, and isolates transactional and analytical loads so that both parties do not interfere with each other under high concurrency pressure.
In addition, BASED on the distributed architecture, TiDB 5.0 supports cloud native and multi-cloud, and can flexibly expand throughput or storage, easily cope with high concurrency, massive data scenarios, and realize a stack of data services. Enterprise users and Internet users can build digital scenarios through a TiDB system, regardless of the underlying architecture. SaaS vendors and INDEPENDENT software developers can also get an agile, easy-to-operate data base through the simplified TiDB technology stack.
The overall performance and stability are enhanced
TiDB has been determined to become an enterprise-level database at the beginning of its design. Its technical architecture of “distributed strong consistent transaction, online elastic horizontal expansion, high availability of fault recovery, cross-data center multi-activity” determines that it has the key characteristics required by enterprise-level core database. TiDB 5.0 represents a significant improvement in performance, achieving an average 50 percent performance improvement in OLTP benchmarks such as Sysbench and TPC-C by providing clustered indexing, asynchronous commit transactions, and more. TiFlash MPP has several times the performance advantage over GreenPlum in OLAP configuration.
At the same time, TiDB 5.0 can greatly reduce the QPS (query per second) jitter problem caused by resource preemption by optimizing the utilization of I/O, network, CPU, memory and other resources during the scheduling process. In the benchmark test of TPC-C OLTP, The standard deviation of jitter of TPC-C tpmC is less than or equal to 2%.
A more open user ecosystem
PingCAP has been taking open source as its core strategy since its establishment. The highly active open source community has brought flywheel effect to the development of TiDB products. At present, TiDB’s research and development capability, engineering quality and iteration speed are all at the leading level in the world. TiDB is also an eco-friendly database. TiDB 5.0 integrates a richer big data ecosystem, adds Kafka connectors, supports S3 storage services, and provides multiple data migration, import and sharing components, making it easy for users to use TiDB in their own heterogeneous environment.
TiDB, with its leading technical capabilities and perfect commercial service support system, helps users in finance, Internet, retail, logistics, manufacturing, public service and other industries to build future-oriented data service platforms. TiDB is currently used in more than 1500 head companies worldwide. Including the bank of China, everbright bank, Shanghai pudong development bank, zheshang bank, bank of Beijing, the bank, bank, China unionpay, China life, ping an life insurance, Lu Jin, China mobile, China unicom, China telecom, China jun choi, state grid, ideal car, xiao peng car, VIVO, OPPO, yum China, China post, suitable abundant speed luck, zhongtong express , Tencent, Meituan, JD, Pinduoduo, Xiaomi, Sina Weibo, 58.com, 360, Zhihu, IQiyi, Bilibili, Square (US), Dailymotion (France), Shopee (Singapore), ZaloPay (Vietnam), BookMyShow (India), etc.
PingCAP co-founder and CTO Huang Dongxu said: “a real enterprise database vendors should put themselves in the user’s point of view to think, whether to buy an enterprise database digital challenge, or an engineer to the hundreds of database cluster maintenance, I think they need to do is” worry, rest assured, don’t worry. TiDB 5.0 is a milestone release with full HTAP capabilities that enables users to respond to the “massive, real-time, online” business needs of digital transformation, whether transactional or analytical.