Citus vs TimescaleDB

Need advice about which tool to choose?Ask the StackShare community!


+ 1

+ 1
Add tool

Citus vs TimescaleDB: What are the differences?

Developers describe Citus as "Worry-free Postgres for SaaS. Built to scale out". Citus is worry-free Postgres for SaaS. Made to scale out, Citus is an extension to Postgres that distributes queries across any number of servers. Citus is available as open source, as on-prem software, and as a fully-managed service. On the other hand, TimescaleDB is detailed as "Scalable time-series database optimized for fast ingest and complex queries. Purpose-built as a PostgreSQL extension". TimescaleDB is the only open-source time-series database that natively supports full-SQL at scale, combining the power, reliability, and ease-of-use of a relational database with the scalability typically seen in NoSQL databases.

Citus and TimescaleDB belong to "Databases" category of the tech stack.

Some of the features offered by Citus are:

  • Multi-Node Scalable PostgreSQL
  • Built-in Replication and High Availability
  • Real-time Reads/Writes On Multiple Nodes

On the other hand, TimescaleDB provides the following key features:

  • Packaged as a PostgreSQL extension
  • Full ANSI SQL
  • JOINs (e.g., across PostgreSQL tables)

Citus and TimescaleDB are both open source tools. It seems that TimescaleDB with 7.28K GitHub stars and 385 forks on GitHub has more adoption than Citus with 3.64K GitHub stars and 273 GitHub forks.

Advice on Citus and TimescaleDB
Umair Iftikhar
Technical Architect at ERP Studio · | 3 upvotes · 312.4K views
Needs advice

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.

See more
Replies (1)

Hi Umair, Did you try MongoDB. We are using MongoDB on a production environment and collecting data from devices like your scenario. We have a MongoDB cluster with three replicas. Data from devices are being written to the master node and real-time dashboard UI is using the secondary nodes for read operations. With this setup write operations are not affected by read operations too.

See more
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

See more
Replies (3)
Yaron Lavi

We had a similar challenge. We started with DynamoDB, Timescale, and even InfluxDB and Mongo - to eventually settle with PostgreSQL. Assuming the inbound data pipeline in queued (for example, Kinesis/Kafka -> S3 -> and some Lambda functions), PostgreSQL gave us a We had a similar challenge. We started with DynamoDB, Timescale and even InfluxDB and Mongo - to eventually settle with PostgreSQL. Assuming the inbound data pipeline in queued (for example, Kinesis/Kafka -> S3 -> and some Lambda functions), PostgreSQL gave us better performance by far.

See more

Druid is amazing for this use case and is a cloud-native solution that can be deployed on any cloud infrastructure or on Kubernetes. - Easy to scale horizontally - Column Oriented Database - SQL to query data - Streaming and Batch Ingestion - Native search indexes It has feature to work as TimeSeriesDB, Datawarehouse, and has Time-optimized partitioning.

See more
Ankit Malik
Software Developer at CloudCover · | 3 upvotes · 226.4K views
Google BigQueryGoogle BigQuery

if you want to find a serverless solution with capability of a lot of storage and SQL kind of capability then google bigquery is the best solution for that.

See more
Decisions about Citus and TimescaleDB
Benoit Larroque
Principal Engineer at Sqreen · | 2 upvotes · 102.3K views

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

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Citus
Pros of TimescaleDB
  • 6
    Multi-core Parallel Processing
  • 2
    Drop-in PostgreSQL replacement
  • 2
    Distributed with Auto-Sharding
  • 8
    Open source
  • 7
    Easy Query Language
  • 6
    Time-series data analysis
  • 5
    Established postgresql API and support
  • 4
  • 2
    Chunk-based compression
  • 2
  • 2
    Paid support for automatic Retention Policy
  • 2
    Postgres integration
  • 2
    Fast and scalable
  • 1
    Case studies

Sign up to add or upvote prosMake informed product decisions

Cons of Citus
Cons of TimescaleDB
    Be the first to leave a con
    • 5
      Licensing issues when running on managed databases

    Sign up to add or upvote consMake informed product decisions

    What is Citus?

    It's an extension to Postgres that distributes data and queries in a cluster of multiple machines. Its query engine parallelizes incoming SQL queries across these servers to enable human real-time (less than a second) responses on large datasets.

    What is TimescaleDB?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Citus and TimescaleDB as a desired skillset
    What companies use Citus?
    What companies use TimescaleDB?
    See which teams inside your own company are using Citus or TimescaleDB.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Citus?
    What tools integrate with TimescaleDB?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Citus and TimescaleDB?
    CockroachDB is distributed SQL database that can be deployed in serverless, dedicated, or on-prem. Elastic scale, multi-active availability for resilience, and low latency performance.
    Apache Aurora
    Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation.
    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.
    It is a database solution for deploying, scaling and managing large clusters of MySQL instances. It’s architected to run as effectively in a public or private cloud architecture as it does on dedicated hardware. It combines and extends many important MySQL features with the scalability of a NoSQL database.
    It allows analysis of data that is updated in real time. It offers instant results in most cases: the data is processed faster than it takes to create a query.
    See all alternatives