All systems operational · 99.99% uptime SLA
TiDB — Distributed SQL · HTAP · MySQL Compatible

One database
for transactions
AND analytics.

TiDB is a distributed NewSQL database that handles OLTP and OLAP workloads simultaneously — no ETL pipeline, no separate data warehouse, no Hadoop. MySQL-compatible, Raft-based financial-grade HA, and horizontal scale to 512 nodes and PB-level storage.

512nodeMax compute
PBStorage scale
RPO=0Raft consensus
RTO≤30sAuto-failover
OLTP Transactions INSERT / UPDATE SELECT · JOIN BEGIN · COMMIT Row store · TiKV OLAP Analytics GROUP BY · AVG Window Functions Real-time Reports Column store · TiFlash TiDB Server SQL Layer · MySQL Protocol · Stateless PD Orchestration · Raft TiKV Row Store TiKV Node 1 TiKV Node 2 TiKV Node 3 TiFlash Column Store Flash Node 1 Flash Node 2 Flash Node 3 Async Repl HTAP One database · No ETL MySQL Compatible · 100% ACID Raft Consensus · RPO=0 · RTO≤30s 512 Nodes · PB-level Storage
Performance & Scale

The numbers that make TiDB enterprise-grade

Distributed architecture built for the scale problems that single-node databases can't solve — measured, verified, and deployed in financial institutions across the region.

512
Max compute nodes
Scale TiDB compute nodes to 512 — each supporting 1,000 concurrent connections. Horizontal scale by simply adding nodes, no sharding middleware, no application changes.
PB
Cluster storage capacity
TiKV storage scales to PB-level. With 5G, IoT, and AI producing hundreds of TB or even PB of data, TiDB's distributed storage expands to meet demand transparently.
RPO=0
Zero data loss on failure
Raft majority election guarantees 100% financial-grade data consistency. Recovery Point Objective of zero — no data loss under any single-node failure scenario.
RTO≤30s
Auto-failover recovery time
When nodes fail, the Raft protocol automatically elects new leaders and recovers the cluster — no human intervention required — within 30 seconds of the failure event.
100%
ACID transaction support
TiDB supports full standard ACID distributed transactions across all nodes in the cluster. Financial-grade consistency for the most demanding transactional workloads.
1K
Concurrent connections/node
Each TiDB compute node handles 1,000 concurrent connections. With 512 nodes, the cluster supports 512,000 simultaneous connections — well beyond any single-node database limit.
Core Capabilities

Five reasons teams choose TiDB over MySQL and Hadoop

TiDB doesn't replace your database — it replaces your database AND your data warehouse, while running MySQL-compatible SQL throughout.

MySQL Compatible — Migrate Without Code Changes

Migrate from MySQL to TiDB without modifying a single line of application code. MySQL clusters using sharding middleware can be migrated in real-time using TiDB's synchronization tools — same SQL, same drivers, same ORM.

HTAP — Transactions AND Analytics in One

TiKV handles row-based OLTP writes while TiFlash (column store) serves real-time analytical queries — from the same data, in the same cluster. No ETL, no replication lag, no data warehouse to build and maintain.

Dynamic Horizontal Expansion

Add TiDB compute nodes or TiKV storage nodes independently to increase throughput or capacity as needed. No complex resharding, no application downtime, no migration — expansion is fully transparent to applications.

Financial-grade Raft Consensus HA

Unlike master-slave replication where failover risks data loss, Raft majority election provides 100% strong data consistency guarantees. RPO=0 and RTO≤30s with automatic failover — no manual intervention, no risk of split-brain.

100% Distributed ACID Transactions

TiDB supports the complete ACID standard across all distributed nodes — not eventual consistency, not partial ACID. Multi-table, multi-node transactions work exactly as you'd expect from a single-node RDBMS.

TiDB Serverless — Zero-ops Option

Serverless mode auto-scales compute and storage based on actual load — no cluster configuration required. Three tiers: Trial (free), Lite (fixed small cluster), and Flagship (auto-scaling, production-ready). Focus entirely on your application.

HTAP — Hybrid Transactional/Analytical Processing

One database replaces two. No ETL required.

The traditional approach forces you to maintain two separate systems — an OLTP database for transactions and an OLAP warehouse for analytics, connected by expensive ETL pipelines. TiDB eliminates this entirely.

TiDB 4.0+ · TiKV + TiFlash

Transactions write to TiKV.
Analytics read from TiFlash.
Same data. Same cluster.

When you write a transaction to TiDB, it goes to TiKV (row-based storage). TiFlash asynchronously replicates the data in columnar format. Your analytics queries automatically route to TiFlash — getting columnar scan performance without any ETL, without any data pipeline, and without any replication lag waiting period.

For enterprises currently running ETL + Hadoop or ETL + data warehouse: TiDB's HTAP eliminates that entire architecture. Business data synchronised from multiple source systems can be aggregated and reported on in real time — T+0, not T+1.

Learn About TiFlash →
TiKV — Row Storage EngineStandard row-based storage optimised for OLTP — INSERT, UPDATE, DELETE, point queries. The primary storage layer for all transactional writes. Data is sharded automatically across TiKV nodes using Raft groups.
TiFlash — Column Storage EngineColumnar storage automatically replicated from TiKV in real time. Optimised for OLAP — full table scans, GROUP BY, window functions, and aggregations run 10–100× faster on columnar data. No ETL, no delay.
PD — Placement DriverThe orchestration layer that manages cluster topology, load balancing, and Raft leader election. PD ensures data is evenly distributed across nodes and automatically rebalances when nodes are added or removed.
Raft-based High Availability

Financial-grade consistency. Automatic recovery.

Unlike master-slave replication where failover can lose committed transactions, TiDB's Raft majority election guarantees that data is committed only when a majority of replicas acknowledge it. No data loss is possible from a single-node failure.

  • Raft majority election — data committed only when majority confirms
  • RPO = 0 — zero data loss on any single-node failure
  • RTO ≤ 30s — automatic leader election and service recovery
  • Multiple data centers, racks, and machines — data distributed by PD
  • No manual intervention required on node failure or recovery
  • Eliminates traditional 2-datacenter active-passive limitations
Read Architecture Docs →
TiDB Server (SQL Layer)Stateless · MySQL protocol · Scales independently
Running
PD — Placement DriverCluster orchestration · Raft leader election · Load balancing
Orchestrating
TiKV — Row Storage (Raft Groups)OLTP writes · Distributed key-value · Multi-replica
3+ Replicas
TiFlash — Column Storage (OLAP)Real-time analytics · Asynchronous replication from TiKV
In-sync
Raft Consensus LayerMajority election · No split-brain · Auto leader promotion
Consensus
RPO=0Zero Data Loss
RTO≤30sAuto Recovery
100%ACID
Instance Types

Dedicated or Serverless. Your TiDB, your way.

Choose fully customizable dedicated clusters for maximum control, or TiDB Serverless for zero-configuration deployment that auto-scales to your workload.

Dedicated
TiDB Dedicated
Custom cluster · Full control
  • Configure compute nodes, storage nodes, and TiFlash independently
  • Choose CPU:Memory ratio for each node type
  • Scale to 512 compute nodes, PB storage
  • Full Binlog sync, TiFlash, Dashboard access
  • VPC isolation · Security groups
Serverless
Trial
3 compute + 3 storage nodes · Fixed
  • 3 compute nodes · 4 GB memory each
  • 3 storage nodes · 10 GB memory, 200 GB RSSD each
  • No cluster configuration required
  • Automatic failover included
  • Best for testing and small workloads
Serverless
Lite
3 compute + 3 storage nodes · Fixed
  • 3 compute nodes · 8 GB memory each
  • 3 storage nodes · 20 GB memory, 400 GB RSSD each
  • No cluster configuration required
  • Automatic failover included
  • Best for lightweight online workloads
TiDB vs Alternatives

Why TiDB wins when MySQL alone isn't enough

When your data volume exceeds what a single MySQL node can serve — and your analytics needs can't wait for nightly ETL — TiDB is the upgrade path.

CapabilityNubexCloud TiDBMySQL (Single Node)MySQL + Data Warehouse
MySQL SQL compatibility✓ 100% compatible✓ Native✓ Native
Horizontal scale✓ 512 nodes, PB storage✗ Single node limit~ Complex sharding
HTAP (OLTP + OLAP)✓ TiKV + TiFlash, one cluster✗ OLTP only~ Separate system + ETL
Real-time analytics✓ T+0, no ETL delay✗ Not supported✗ T+1 ETL delay
ACID distributed transactions✓ 100% across all nodes✓ Single node✗ Cross-system not ACID
HA without data loss✓ Raft · RPO=0~ Master-slave · Risk of loss~ Depends on config
Auto-failover✓ <30s, no intervention~ Manual or semi-auto~ Complex multi-system
Infrastructure complexity✓ One managed system✓ Simple✗ Two systems + ETL ops
Storage cost at PB scale✓ Efficient, one cluster✗ Impractical✗ Double storage cost
Application Scenarios

Where TiDB replaces entire data architectures

TiDB is designed for problems that traditional databases solve with complexity — sharding middleware, ETL pipelines, and separate OLAP systems. TiDB handles them natively.

Global Network

A truly global infrastructure for fast, reliable service delivery.

26
Regions
33
Availability Zones
25ms
Regional latency
99.95%
SLA uptime
Active region
Hub region (Dubai HQ)
Backbone link
Customer Stories

What teams are building on TiDB

Trusted by leading teams across the region
Falcon AITradeSparkMasaarNEXAGENSalam DigitalOrbita
Billing

Three billing modes for TiDB Dedicated clusters.

TiDB Serverless billing adjusts automatically with your workload. Dedicated clusters use the same hourly, monthly, or annual model as all NubexCloud databases.

Best for dev/test

Hourly

1.5× daily rate

  • Spin up a TiDB cluster for load testing, destroy after results
  • Evaluate HTAP performance before committing to monthly
  • No minimum term per node type
Maximum savings

Annual Prepay

Pay 10 months, get 12

  • 17% discount — for long-running production clusters
  • Lock in rates for all node types for the full year
  • Best cost/performance for financial and data platform workloads

Each node type billed independently.

TiDB Server nodes, TiKV storage nodes, and TiFlash column-store nodes are each billed separately by their CPU, memory, and disk specification. This allows you to scale compute and storage independently and pay only for what you use.

FAQ

Common questions about TiDB

Start building today

One database for everything. No ETL required.

MySQL-compatible. Distributed to PB scale. HTAP with TiFlash. Raft-based RPO=0. Deploy TiDB Serverless in minutes or configure a dedicated cluster to your exact specifications.

Deploy TiDB Free → Read the Docs