PROVIDER Β· MySQL-compatible HTAP database

TiDB Cloud

TiDB Cloud is PingCAP's managed open-source distributed HTAP database compatible with MySQL, combining TiKV row storage and TiFlash columnar storage for realtime analytics on operational data.

Backend & Database China 2026.11.15
Backend & Database China MySQL-compatible HTAP database
4.2pts

Pros

4 items
MySQL protocol compatibility so most clients and ORMs connect directly
Row and columnar storage (TiKV and TiFlash) coexist for transactions and realtime analytics
Separated compute and storage support online horizontal scaling
Both managed TiDB Cloud and open-source self-hosting are available

Cons

4 items
Distributed components need specialised experience to deploy, tune, and debug, raising the self-hosting bar
Node and storage billing yields unfavourable unit cost at small scale
Overseas community and English material are thinner, leaning on vendor support
Advanced MySQL features and plans differ, requiring thorough regression testing

Product Information

tidb-cloud
Category Backend & Database
Company TiDB Cloud
Service Region China
Recommendation Score 4.2 pts
Published 2026-11-15

Detailed Notes

Overview

TiDB is an open-source distributed HTAP database initiated by China's PingCAP team and compatible with MySQL. It keeps row storage in TiKV and columnar storage in TiFlash within one system so OLTP and OLAP run on the same data, removing export pipelines to an analytics database.

For Backend & Database work its value is realtime reporting without hurting the transactional path, since member and order data sits in TiDB while heavy aggregation runs on TiFlash replicas. For MySQL shops, protocol compatibility keeps migration comparatively contained.

The limits are operational and cost thresholds, since distributed components need experience and self-hosting demands a capable team, cloud plans bill by node size and storage with poor unit economics at small scale, and overseas community material trails the Chinese ecosystem.

Core Strengths

  • MySQL protocol compatibility so most clients and ORMs connect directly
  • Row and columnar storage (TiKV and TiFlash) coexist for transactions and realtime analytics
  • Separated compute and storage support online horizontal scaling
  • Both managed TiDB Cloud and open-source self-hosting are available

Product Ecosystem

TiKV and TiFlash

Row storage handles transactional writes while columnar replicas serve aggregation, routed by query. Reserve resources for TiFlash or analytics degrade to row scans.

Elastic scaling

Compute nodes scale with load and storage expands independently, with hot region distribution watched during changes.

Migration and compatibility

MySQL syntax and protocol work, though advanced features and plans differ, so replay real SQL before migrating.

Drawbacks

  • Distributed components need specialised experience to deploy, tune, and debug, raising the self-hosting bar
  • Node and storage billing yields unfavourable unit cost at small scale
  • Overseas community and English material are thinner, leaning on vendor support
  • Advanced MySQL features and plans differ, requiring thorough regression testing

Use Cases

  • Realtime reporting on the operational database (β˜…β˜…β˜…β˜…β˜…) - HTAP removes export pipelines
  • Existing MySQL stacks (β˜…β˜…β˜…β˜…) - Protocol compatibility smooths migration
  • Very small applications (β˜…β˜…) - Single-node MySQL or Postgres is cheaper
  • Teams wanting minimal operations (β˜…β˜…β˜…) - Use the managed cloud rather than self-hosting

Pricing

Plan Price Scope
Serverless and entry tiers From $0 Limited capacity and requests
Node-based billing Per size and count Includes storage and backups
Enterprise Custom quote Dedicated clusters and support

Billing follows node size and storage with tiers on the official site. Budget TiFlash replica resources separately, since counting only TiKV underestimates cost while disabling TiFlash pushes analytics onto the transactional path.

FAQ

  • What is HTAP? A single database handling both transactional and analytical workloads. TiDB achieves it with row and columnar replicas, avoiding exports to a warehouse.

  • Is it fully MySQL compatible? Protocol and common syntax work, though some advanced features and plans differ, so replay critical SQL before migrating.

  • Is self-hosting hard? It requires understanding distributed components and tuning, so managed cloud suits production while self-hosting fits teams with a dedicated DBA.

Visit TiDB Cloud Website β†’ https://www.pingcap.com/tidb-cloud/
Visit Website β†—