Softwr

Databases · head to head

Firestore vs TiDB

Firestore logo

Firestore

Databases

Flexible, scalable NoSQL cloud database from Firebase

From
Free
Rated
-
Full reviewWebsite
TiDB logo

TiDB

Databases

Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Firestore the no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day; TiDB a production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
  • They diverge on capability: Firestore covers Document Model, TiDB covers MySQL wire compatibility.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Firestore and TiDB actually diverge.

Attributes where Firestore and TiDB differ
AttributeFirestoreTiDB
PlatformsWeb, Ios, Android, FlutterCloud, AWS, Azure, Google Cloud Platform, Self-managed
Founded20112015

Identical on both: starting price (Free), pricing model (freemium), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Firestore

  • Document Model
  • Real-time Updates
  • Offline Support
  • ACID Transactions
  • Expressive Queries
  • Multi-region
  • Security Rules
  • Firebase Auth

Only in TiDB

  • MySQL wire compatibility
  • Horizontal write scaling
  • Distributed ACID transactions
  • TiFlash columnar replica
  • Automatic rebalancing
  • Raft replication
  • Apache 2.0 licence
  • Online schema change

What people use each for

The jobs each tool is most often brought in to do.

Firestore

  • Storing structured application data with realtime listenersnot TiDB
  • Backing mobile and web apps with a serverless document databasenot TiDB
  • Building offline first apps that sync when connectivity returnsnot TiDB

TiDB

  • A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Firestore
  • Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Firestore
  • Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Firestore
  • Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot Firestore

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Firestore

  • The no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day
  • The Spark plan caps storage at 1 GiB and network egress at 10 GiB per month
  • Charging is per document read, so a query returning many documents bills for every one of them
  • Going beyond the free thresholds requires the pay as you go Blaze plan billed at Google Cloud rates with no fixed monthly ceiling

TiDB

  • A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
  • Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed.
  • MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed.
  • The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately.
  • Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage.

Pricing, plan by plan

Firestore

Free
  • SparkFree
    • 1GB storage
    • 50K reads/day
    • 20K writes/day
  • BlazeFree
    • Pay as you go
    • Unlimited operations
    • Multi-region

TiDB

Free
  • ServerlessFree
    • 5GB storage
    • 50M request units
    • Free forever tier
  • Dedicated$250/month
    • Dedicated resources
    • SLA guarantees
    • Enterprise support

Which should you pick?

Choose Firestore if

  • You need document model.
  • You want to start without paying.
  • You work on Web, Ios, Android, Flutter.
  • You also want real-time updates.
Firestore review

Choose TiDB if

  • You need mysql wire compatibility.
  • You want to start without paying.
  • You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
  • You also want horizontal write scaling.
TiDB review

Questions people ask

Is Firestore or TiDB better?
Neither clearly leads. Firestore starts at Free and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Firestore or TiDB?
Firestore starts at Free and TiDB at Free.
Does Firestore or TiDB run on more platforms?
Firestore runs on Web, Ios, Android, Flutter. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
Can I use Firestore for free?
Both have a free tier, so you can try either at no cost before committing.
What is Firestore best used for?
Firestore is most often used for storing structured application data with realtime listeners, backing mobile and web apps with a serverless document database, building offline first apps that sync when connectivity returns. Of those, storing structured application data with realtime listeners and backing mobile and web apps with a serverless document database are not what TiDB is typically brought in for.
What can Firestore do that TiDB cannot?
Firestore covers Document Model, Real-time Updates, Offline Support, ACID Transactions. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.

Answered from the vendors’ own pages

Firestore: What are the free limits on Cloud Firestore?

The Spark Plan includes 1 GiB of stored data, 50,000 reads per day, 20,000 writes per day, and 20,000 deletes per day at no cost.

Source
TiDB: Is TiDB a drop-in replacement for MySQL?

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.

Firestore: What happens when I exceed the Spark Plan free tier?

Exceeding the free tier requires upgrading to the Blaze Plan, which bills based on actual usage through Google Cloud pricing. Charges apply for reads, writes, deletes, and data storage.

Source
TiDB: What licence is it under?

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.

Firestore: Can I use Firestore without a credit card?

Yes, you can use the Spark Plan indefinitely without a credit card. To use the Blaze Plan (pay-as-you-go), a credit card is required.

Source
TiDB: Do I need TiFlash?

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.

Firestore: Is there a trial period for Cloud Firestore?

No trial period is specified. The Spark Plan free tier serves as the trial, with no time limit.

Source
TiDB: Is the managed cloud the same software?

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.

TiDB: When is TiDB the wrong choice?

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.

Share

Related pages

More on Firestore

More on TiDB

Keep looking

Other head to heads