TiDB — Distributed SQL Database with MySQL Compatibility

What it is

TiDB is an open-source, cloud-native, distributed SQL database that supports hybrid transactional and analytical processing (HTAP). It speaks the MySQL wire protocol, so existing MySQL applications can connect to TiDB with minimal code changes. Under the hood, TiDB separates compute and storage, enabling horizontal scalability, strong consistency, and elastic scaling without manual sharding.

Engineering teams running MySQL at scale who hit single-node limits benefit most from TiDB. It is designed for applications that need both OLTP (transactions) and OLAP (analytics) without maintaining separate databases.

How it saves time or tokens

TiDB eliminates manual sharding, which is the biggest time sink in scaling MySQL. Instead of rewriting application code to route queries across shards, TiDB handles distribution transparently. The HTAP capability removes the need to maintain a separate analytics database and ETL pipeline, saving the engineering time of keeping two systems in sync.

How to use

1. Install TiUP (TiDB's package manager) and start a local playground
2. Connect with any MySQL client using the standard MySQL protocol
3. Scale out by adding TiKV storage nodes or TiDB compute nodes

Example

# Install TiUP
curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh
source ~/.zshrc

# Start a local playground cluster
tiup playground

# Connect with standard MySQL client
mysql -h 127.0.0.1 -P 4000 -u root

# Use standard SQL
CREATE DATABASE myapp;
USE myapp;
CREATE TABLE users (id BIGINT PRIMARY KEY AUTO_RANDOM, name VARCHAR(255));
INSERT INTO users (name) VALUES ('Alice');
SELECT * FROM users;

Related on TokRepo

• AI tools for database — Browse database tools and solutions
• Featured workflows — Discover top-rated workflows across categories

Common pitfalls

• AUTO_INCREMENT behaves differently in distributed mode; use AUTO_RANDOM for primary keys to avoid hotspots
• Some MySQL features (stored procedures, certain window functions) have limited support; check TiDB's compatibility matrix
• A minimum production deployment requires 3 PD nodes, 3 TiKV nodes, and 2 TiDB nodes, which is significant infrastructure