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. TiDB vs TimescaleDB

TiDB vs TimescaleDB

OverviewDecisionsComparisonAlternatives

Overview

TiDB
TiDB
Stacks76
Followers177
Votes28
GitHub Stars39.3K
Forks6.0K
TimescaleDB
TimescaleDB
Stacks227
Followers374
Votes44
GitHub Stars20.6K
Forks988

TiDB vs TimescaleDB: What are the differences?

< Introduction: TiDB and TimescaleDB are both popular databases used for different purposes. TiDB is a distributed SQL database that combines the scalability of NoSQL with the ACID compliance of traditional RDBMS, while TimescaleDB is a time-series database built on top of PostgreSQL. These databases offer distinct features and capabilities tailored to specific use cases.

1. **Storage Model**: TiDB is a distributed, horizontally scalable database that stores data across multiple nodes, providing high availability and fault tolerance. In contrast, TimescaleDB is optimized for efficient storage and querying of time-series data, making it ideal for applications that require analyzing and visualizing time-stamped data over time.

2. **Sharding Strategy**: TiDB uses an automatic sharding strategy to distribute data across nodes based on the hash of the primary key, ensuring balanced data distribution and optimal performance. On the other hand, TimescaleDB utilizes hypertables to automatically partition data by time intervals, enabling efficient data retrieval and aggregation for time-series data.

3. **Data Replication**: TiDB supports data replication through Raft consensus algorithm, ensuring data consistency and fault tolerance by replicating data across multiple nodes. In comparison, TimescaleDB leverages PostgreSQL's native replication capabilities for data redundancy and high availability, making it suitable for applications with stringent data durability requirements.

4. **SQL Compatibility**: TiDB is fully compatible with MySQL syntax and features, allowing easy migration for existing MySQL applications to scale horizontally. Conversely, TimescaleDB extends PostgreSQL's SQL capabilities with functions and operators optimized for time-series data processing, making it convenient for developers familiar with SQL to work with time-series data.

5. **Indexing and Optimization**: TiDB uses distributed indexing and optimization techniques to enhance query performance and scalability, enabling efficient execution of complex queries across multiple nodes. In contrast, TimescaleDB incorporates time-oriented indexing methods like B-trees and space partitioning to accelerate querying and aggregation of time-series data, especially for large datasets.

6. **Consistency Model**: TiDB follows a distributed ACID compliance model with strong consistency guarantees, ensuring that transactions are processed reliably across nodes to maintain data integrity. Meanwhile, TimescaleDB offers flexible consistency levels to balance performance and consistency trade-offs, allowing developers to tune the database's behavior based on specific application requirements.

In Summary, TiDB and TimescaleDB differ in their storage models, sharding strategies, data replication mechanisms, SQL compatibility, indexing techniques, and consistency models, catering to different use cases and workloads in the database ecosystem.

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 TiDB, TimescaleDB

Anonymous
Anonymous

Apr 21, 2020

Needs advice

We are building an IOT service with heavy write throughput and fewer reads (we need downsampling records). We prefer to have good reliability when comes to data and prefer to have data retention based on policies.

So, we are looking for what is the best underlying DB for ingesting a lot of data and do queries easily

381k views381k
Comments
Umair
Umair

Technical Architect at ERP Studio

Feb 12, 2021

Needs adviceonPostgreSQLPostgreSQLTimescaleDBTimescaleDBDruidDruid

Developing a solution that collects Telemetry Data from different devices, nearly 1000 devices minimum and maximum 12000. Each device is sending 2 packets in 1 second. This is time-series data, and this data definition and different reports are saved on PostgreSQL. Like Building information, maintenance records, etc. I want to know about the best solution. This data is required for Math and ML to run different algorithms. Also, data is raw without definitions and information stored in PostgreSQL. Initially, I went with TimescaleDB due to PostgreSQL support, but to increase in sites, I started facing many issues with timescale DB in terms of flexibility of storing data.

My major requirement is also the replication of the database for reporting and different purposes. You may also suggest other options other than Druid and Cassandra. But an open source solution is appreciated.

462k views462k
Comments
Benoit
Benoit

Principal Engineer at Sqreen

Sep 21, 2019

Decided

I chose TimescaleDB because to be the backend system of our production monitoring system. We needed to be able to keep track of multiple high cardinality dimensions.

The drawbacks of this decision are our monitoring system is a bit more ad hoc than it used to (New Relic Insights)

We are combining this with Grafana for display and Telegraf for data collection

155k views155k
Comments

Detailed Comparison

TiDB
TiDB
TimescaleDB
TimescaleDB

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

TimescaleDB: An open-source database built for analyzing time-series data with the power and convenience of SQL — on premise, at the edge, or in the cloud.

Horizontal scalability;Asynchronous schema changes;Consistent distributed transactions;Compatible with MySQL protocol;Written in Go;NewSQL over TiKV;Multiple storage engine support
Packaged as a PostgreSQL extension;Full ANSI SQL;JOINs (e.g., across PostgreSQL tables);Complex queries;Secondary indexes;Composite indexes;Support for very high cardinality data;Triggers;Constraints;UPSERTS;JSON/JSONB;Ability to ingest out of order data;Ability to perform accurate rollups;Data retention policies;Fast deletes;Integration with PostGIS and the rest of the PostgreSQL ecosystem;
Statistics
GitHub Stars
39.3K
GitHub Stars
20.6K
GitHub Forks
6.0K
GitHub Forks
988
Stacks
76
Stacks
227
Followers
177
Followers
374
Votes
28
Votes
44
Pros & Cons
Pros
  • 9
    Open source
  • 7
    Horizontal scalability
  • 5
    Strong ACID
  • 3
    HTAP
  • 2
    Enterprise Support
Pros
  • 9
    Open source
  • 8
    Easy Query Language
  • 7
    Time-series data analysis
  • 5
    Established postgresql API and support
  • 4
    Reliable
Cons
  • 5
    Licensing issues when running on managed databases
Integrations
No integrations available
Prometheus
Prometheus
Equinix Metal
Equinix Metal
Ruby
Ruby
PostgreSQL
PostgreSQL
Django
Django
Kubernetes
Kubernetes
pgAdmin
pgAdmin
Python
Python
Kafka
Kafka
Datadog
Datadog

What are some alternatives to TiDB, TimescaleDB?

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.

MySQL

MySQL

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.

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.

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