StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. MySQL vs TiDB

MySQL vs TiDB

OverviewDecisionsComparisonAlternatives

Overview

MySQL
MySQL
Stacks129.6K
Followers108.6K
Votes3.8K
GitHub Stars11.8K
Forks4.1K
TiDB
TiDB
Stacks76
Followers177
Votes28
GitHub Stars39.3K
Forks6.0K

MySQL vs TiDB: What are the differences?

Introduction

MySQL and TiDB are both popular databases used in web development. While MySQL is a traditional relational database management system, TiDB is a newer distributed SQL database built for scalability and high availability. However, there are key differences between the two that set them apart.

  1. Data Placement: In MySQL, data is typically placed on a single server, whereas TiDB automatically splits and replicates data across multiple servers for better durability and fault tolerance. This allows TiDB to handle large amounts of data and provide high availability without manual sharding or partitioning.

  2. Architecture: MySQL follows a master-slave replication model where a single master handles write operations and multiple slaves handle read operations. On the other hand, TiDB uses a distributed architecture based on the Google Spanner model, with multiple TiKV nodes and TiDB nodes working together to provide horizontal scalability and fault tolerance.

  3. Consistency Model: MySQL follows the strong consistency model, where transactions are ACID-compliant and guarantee data integrity. In contrast, TiDB provides a unique consistency model called "consistency without consensus." It uses a distributed consensus algorithm to achieve linearizability, ensuring global consistency while still maintaining high availability and performance.

  4. SQL Compatibility: MySQL has been around for a long time and has a wide range of SQL compatibility, including support for complex queries, stored procedures, and triggers. While TiDB also supports standard SQL, some advanced features and syntax are still in development or not yet available.

  5. Scalability: MySQL can scale vertically by adding more resources to a single server, but it has limitations in terms of horizontal scalability. TiDB, on the other hand, is designed for horizontal scalability and can easily handle high traffic loads by adding more nodes to the cluster.

  6. Fault Tolerance: In MySQL, fault tolerance is achieved through techniques like replication, failover, and backup/restore. TiDB, being a distributed system, has built-in fault tolerance mechanisms. It distributes data across multiple nodes, automatically replicates data, and can tolerate node failures without data loss.

In summary, MySQL and TiDB differ in terms of data placement, architecture, consistency model, SQL compatibility, scalability, and fault tolerance. While MySQL is a mature RDBMS with extensive SQL compatibility, TiDB offers scalability, fault tolerance, and consistency without consensus in a distributed SQL database system.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on MySQL, TiDB

Kyle
Kyle

Web Application Developer at Redacted DevWorks

Dec 3, 2019

DecidedonPostGISPostGIS

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

449k views449k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Navraj
Navraj

CEO at SuPragma

Apr 16, 2020

Needs adviceonMySQLMySQLPostgreSQLPostgreSQL

I asked my last question incorrectly. Rephrasing it here.

I am looking for the most secure open source database for my project I'm starting: https://github.com/SuPragma/SuPragma/wiki

Which database is more secure? MySQL or PostgreSQL? Are there others I should be considering? Is it possible to change the encryption keys dynamically?

Thanks,

Raj

401k views401k
Comments

Detailed Comparison

MySQL
MySQL
TiDB
TiDB

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

Inspired by the design of Google F1, TiDB supports the best features of both traditional RDBMS and NoSQL.

-
Horizontal scalability;Asynchronous schema changes;Consistent distributed transactions;Compatible with MySQL protocol;Written in Go;NewSQL over TiKV;Multiple storage engine support
Statistics
GitHub Stars
11.8K
GitHub Stars
39.3K
GitHub Forks
4.1K
GitHub Forks
6.0K
Stacks
129.6K
Stacks
76
Followers
108.6K
Followers
177
Votes
3.8K
Votes
28
Pros & Cons
Pros
  • 800
    Sql
  • 679
    Free
  • 562
    Easy
  • 528
    Widely used
  • 490
    Open source
Cons
  • 16
    Owned by a company with their own agenda
  • 3
    Can't roll back schema changes
Pros
  • 9
    Open source
  • 7
    Horizontal scalability
  • 5
    Strong ACID
  • 3
    HTAP
  • 2
    Enterprise Support

What are some alternatives to MySQL, TiDB?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

InfluxDB

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase