TiDB review

TiDB is an open-source distributed SQL database, available as a self-managed server or as TiDB Cloud, a managed service. It sits in the data layer behind applications: services send SQL queries to store transactional records, run analytics, or retrieve vector-search results. The vendor also offers TiDB Cloud Lake, a managed analytics and search warehouse.

The architectural pitch is to combine transactions, analytics and vector search rather than move data among separate systems. TiDB supports joining vector similarity results directly with transactional data. For agent workloads, the vendor describes ACID consistency across workflow steps and distributed nodes, tenant-scoped data separation, and dedicated throughput. Its elastic scaling is described as adapting from zero when idle to peak demand. Those features may reduce the need for separate data stores, but the actual deployment choice matters: managed TiDB Cloud and self-managed TiDB put different infrastructure and operational responsibilities on the team.

The primary integration surface is SQL. The homepage says developers can use familiar MySQL or PostgreSQL tools, and describes TiDB as a distributed SQL database. It also lists integrations for MCP, pytidb, LangChain and LlamaIndex. The homepage does not name programming-language SDKs; confirm supported languages and client compatibility in the vendor's documentation before selecting a stack.

For AI agents, PingCAP provides an MCP server connection example using npx mcp-remote and https://tidb.link/mcp. The example configures an MCP client to connect to TiDB Cloud and describes actions such as creating a branch, running a SQL query and viewing slow queries. This is an integration example, not a general TiDB command-line interface. The homepage links to a Developer Hub and documentation, but teams should verify the exact APIs, SDK versions, connection methods and operational guidance there. Online DDL and zero-downtime schema changes are listed as developer features.

TiDB Cloud Starter costs $0 per month and includes 25 GiB of row storage, 25 GiB of columnar storage, 250 million Request Units monthly, and allowances across up to five eligible instances. Usage beyond those allowances starts at $0.10 per million RUs, $0.20 per GiB-month for row storage and $0.05 per GiB-month for columnar storage.

Essential starts at $400 per month for compute; Premium starts at $1,800. Both charge extra for storage, backups, data transfer and other services, with prices varying by region, configuration and usage. Dedicated TiDB Cloud clusters start at $1,376 per month, with final pricing depending on provider, region, configuration and services. For TiDB Cloud Lake, Personal compute starts at $1.60 per hour and Business at $2.40; storage is $23 per TB-month, with cloud-service charges per 10,000 API requests. Lake compute is billed by the second while running. Data integration costs extra, and BYOC adds TiDB Cloud service and support fees on top of cloud-provider infrastructure. No annual billing is listed.

PingCAP describes TiDB as open source and offers TiDB Self-Managed for deployment on your own infrastructure. The homepage does not name the software license, so check the repository and license terms before using TiDB in a product or distributing modified versions. Self-hosting avoids a managed-service dependency, but your team is responsible for the infrastructure and operations; the published pricing details do not provide a self-hosting cost estimate.

SQL access through familiar MySQL or PostgreSQL tools may help reduce application-level migration work, but it does not establish full compatibility or guarantee a straightforward move. The vendor's homepage does not describe data-export formats or a migration path away from TiDB Cloud. Ask PingCAP about export tooling, supported formats, consistency during export and any limits on moving data between managed and self-managed deployments. Check how application code uses vector search and TiDB-specific features before estimating lock-in.

The Starter tier has defined monthly allowances, but the pricing details do not publish request-rate limits. Essential lists autoscaling within a compute limit and point-in-time recovery; Premium lists isolated compute, storage and network, private connectivity, customer-managed keys, and 99.99% availability with multi-zone protection. Confirm which options apply to your region and configuration, and what service-level terms accompany the availability figure.

The vendor describes scaling from zero to peak and independent scaling of compute and storage. Model the bill against actual workload patterns: storage, backups, data transfer and other services can be extra, while TiDB Cloud Lake has separate compute, storage and cloud-service charges. Encryption in transit and at rest is listed for Essential. The homepage does not list compliance attestations or rate-limit figures, so ask for the relevant security documents and quota details before a production launch. For self-managed deployments, plan for the infrastructure and operational work that the managed plans include.