Sharding Is Dying? Why TiDB Pulls Distribution Back Into the Database
Teams that have hit MySQL's single-node ceiling can skip the sharding maintenance treadmill entirely: no shard rules to tune, no cross-shard JOIN stitching, no T+1 sync pipelines, because a distributed database handles all of that internally. The catch is a different operational model and missing MySQL features, so adoption hinges on whether your workload depends on stored procedures or full-text search.
Traditional MySQL sharding layers routing on top of single instances, forcing developers to maintain shard rules, hand-stitch cross-shard queries, and orchestrate migrations. TiDB removes that work by making distribution a database-internal concern: data splits into ~96MB Regions, PD schedules them across TiKV nodes, and Raft guarantees strong consistency with automatic failover.
TiDB also brings HTAP to the same entry point. TiKV handles OLTP row reads and writes while TiFlash, a columnar engine, syncs in real time via Raft Learner, so analytical queries run without a separate Hive or ClickHouse pipeline. The migration path stays short: JDBC and most SQL carry over, the port changes from 3306 to 4000, and cross-database JOINs just work.
The trade-offs are real. Stored procedures, triggers, full-text indexes, and spatial types are unsupported, operational concepts differ (PD, Region, Raft), and resource consumption beats MySQL for small workloads. For teams already feeling sharding's pain, the article argues TiDB's auto-scaling and online DDL outweigh those costs.
The article frames sharding as an application-layer burden, and the real argument is that a distributed database eliminates an entire class of operational toil rather than just moving it elsewhere.
HTAP is the strongest differentiator: running analytical queries fresh on the same data store removes the latency and consistency problems that T+1 pipelines introduce, but at the cost of more infrastructure.
MySQL compatibility is both a selling point and a trap: teams that lean on stored procedures, triggers, or full-text search face a nontrivial migration, and the port change is the easy part.
The AI-assisted slow-query workflow demonstrates that AI's practical value here is in explaining execution plans and suggesting indexes, while the human still weighs write overhead against query gains.
Resource consumption makes TiDB the wrong default for small workloads; the decision hinges on data volume and operational capacity, not on liking distributed systems.