TiDBvs
Cockroach Labs


Cockroach Labs: Distributed SQL with Postgres compatibility and multi-region-first architecture for cloud-native applications

Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.
As of 30 August 2026, TiDB is free to use. TiDB scales MySQL-compatible OLTP horizontally by separating a stateless SQL layer from a distributed key-value store, and adds a columnar replica so analytical queries do not fight transactional ones. Softwr lists it under Databases. TiDB is made by PingCAP, launched in 2015, available on Web.
Overview
TiDB is a distributed SQL database from PingCAP, licensed Apache 2.0. It is built from separate components: TiDB, a stateless SQL layer that speaks the MySQL wire protocol; TiKV, a distributed transactional key-value store that shards data into ranges replicated by Raft; PD, the placement driver that tracks region metadata, rebalances data and issues the timestamps that order transactions; and TiFlash, an optional columnar replica kept in sync through Raft learners. Applications connect with an ordinary MySQL driver. Because the columnar copy is maintained by the same replication mechanism as the row store, analytical queries can be routed to it without an ETL pipeline or a separate warehouse, which is what the hybrid transactional and analytical claim rests on. TiDB Cloud offers managed deployments, and more recent releases add vector search alongside the relational engine. The distinguishing property is that it scales writes horizontally while remaining something an application already speaks to. MySQL scales reads with replicas easily and writes only by sharding, which pushes routing, cross-shard queries and resharding into the application; TiDB moves that into the database and keeps ACID transactions across the whole cluster. Commercially, that is the difference between a sharding project and a migration, and it is why TiDB shows up in companies that hit the write ceiling of a single MySQL primary and do not want to write a sharding layer. The Apache 2.0 licence matters too, because in a market where several distributed databases moved to source-available terms, TiDB and TiKV, which is a CNCF graduated project, stayed permissive. The buyers are teams with a large MySQL workload that has outgrown vertical scaling, and teams that need fresh analytical queries over transactional data without a pipeline. The trade-off is footprint and latency. A credible production cluster is several PD, TiKV and TiDB nodes rather than a database server, which means it is never the cheap option at small scale; and every transaction pays for distributed consensus and a timestamp from PD, so a simple primary-key lookup that MySQL answers in well under a millisecond is measurably slower here. You buy horizontal scale by giving up the latency floor and the small footprint.
The honest half
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about TiDB.
Cross-shopped
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.


Cockroach Labs: Distributed SQL with Postgres compatibility and multi-region-first architecture for cloud-native applications


Vitess: MySQL sharding middleware for teams that want full control over data partitioning strategy
Pricing
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Serverless
Free
Dedicated
$250 /mo
Capabilities
MySQL wire compatibility
Existing MySQL drivers, ORMs and clients connect without change
Horizontal write scaling
Data is split into ranges spread across TiKV nodes, so write capacity grows by adding nodes
Distributed ACID transactions
Cross-node transactions with snapshot isolation, ordered by timestamps from the placement driver
TiFlash columnar replica
A column-oriented copy maintained by the same replication path, used for analytical queries
Automatic rebalancing
The placement driver moves and splits ranges as data and load change, without manual resharding
Raft replication
Each range is replicated across nodes and failover happens without operator intervention
Apache 2.0 licence
Permissive open source for both TiDB and TiKV, with TiKV a graduated CNCF project
Online schema change
DDL applied without locking the table for the duration of the change
Change data capture
TiCDC streams changes out to downstream systems for replication or integration
Managed cloud
TiDB Cloud provides hosted clusters, including a serverless-style entry tier
Answered, with sources
Each answer names the page it came from, so you can check it rather than take our word for it.
At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.
Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.
Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.
TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.
When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.
Behind it
Timeline
Keep looking
Scalable database clustering system for horizontal scaling of MySQL
The heart of the Elastic Stack for search and analytics
The real-time distributed SQL database for data-intensive applications
Google Cloud's serverless analytical warehouse, billed either by bytes scanned per query or by reserved compute slots.
MIT-licensed analytical SQL database that runs inside your process, with no server, no dependencies and one writer at a time.
Fast open-source column-oriented database for real-time analytics
Time-series database built on PostgreSQL for real-time analytics
Streaming database that maintains incremental materialised views in SQL instead of Flink jobs
Multi-protocol event broker sold as software, cloud service or a hardware appliance
Apache 2.0 MPP analytical database built for joins on open table formats
Softwr does not host reviews and shows no star rating for TiDB, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
What people switch to, and what they give up
Every tier, and where the cost actually lands
Put it head to head with anything we hold
Its rating, and an embed for your own site
Industrial process historian with published per-tag pricing and no client licence fees
Per tag band per yearNetApp-owned managed service for Cassandra, Kafka, OpenSearch, PostgreSQL and Cadence with a bring-your-own-cloud model
quoteErlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node
Per month by connection and session volumeAttribute-based access control and masking applied inside Snowflake, Databricks and BigQuery
quoteMPP analytical database with a MySQL wire protocol and sub-second aggregation on wide tables
Open source, no licence feeStreaming database that maintains incremental materialised views in SQL instead of Flink jobs
Per RisingWave Unit hourCentralised data access governance from the creators of Apache Ranger, now rebranding as Trust3 AI
quoteThe Meta-lineage distributed SQL query engine, distinct from the Trino fork
Open source, no licence fee