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 QuestDB

MySQL vs QuestDB

OverviewDecisionsComparisonAlternatives

Overview

MySQL
MySQL
Stacks129.6K
Followers108.6K
Votes3.8K
GitHub Stars11.8K
Forks4.1K
QuestDB
QuestDB
Stacks19
Followers50
Votes17
GitHub Stars16.3K
Forks1.5K

MySQL vs QuestDB: What are the differences?

Key Differences Between MySQL and QuestDB

MySQL and QuestDB are both relational database management systems (RDBMS) with their own unique features and functionalities. Below are the key differences between MySQL and QuestDB:

  1. Performance: QuestDB is specifically optimized for handling time-series data, providing exceptionally fast write and query speeds. It is capable of ingesting millions of data points per second and executing complex queries within milliseconds. On the other hand, while MySQL is a highly popular and reliable RDBMS, it might not offer the same level of performance for time-series data as QuestDB.

  2. Data Compression: QuestDB utilizes advanced data compression techniques, such as aggressive bit packing and delta encoding, to store and retrieve time-series data more efficiently. This allows for significant reduction in storage requirements and faster data access. MySQL, on the other hand, implements compression techniques, but they might not be as optimized for time-series data as QuestDB.

  3. SQL Support: Both MySQL and QuestDB support SQL, the standard language for managing relational databases. However, QuestDB offers an extended and optimized version of SQL specifically designed for efficient querying of time-series data. It includes features such as sliding windows, temporal joins, and more, which are not natively available in MySQL.

  4. Columnar Storage: QuestDB stores data in a columnar format, which is highly suited for time-series data. This allows for efficient data compression, as well as faster query execution by retrieving only the required columns instead of entire rows. MySQL, on the other hand, uses a row-based storage format by default, which might not offer the same level of efficiency for time-series data.

  5. Scalability: QuestDB is built with scalability in mind, offering horizontal scalability through distributed deployment across multiple nodes. It can easily handle large volumes of data and support high data ingest rates without sacrificing performance. MySQL, although it can also scale horizontally, might require additional configurations and optimization to achieve the same level of scalability as QuestDB.

  6. Open Source: MySQL is an open-source RDBMS, allowing users to freely use, modify, and distribute the software. It has a large and active community, providing continuous support and updates. QuestDB, on the other hand, is also open-source but relatively newer compared to MySQL. It is actively developed and maintained by a smaller community, which might have an impact on the availability of features and support.

In summary, QuestDB provides superior performance and efficiency for handling time-series data compared to MySQL, with optimized query execution, advanced data compression, and columnar storage. However, MySQL offers broader community support, extensive features beyond time-series data, and a more established user base.

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, QuestDB

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
QuestDB
QuestDB

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.

QuestDB is an open source database for time series, events, and analytical workloads with a primary focus on performance. It enhances ANSI SQL with time series extensions.

-
Relational model for time series; SIMD accelerated queries; Time partitioned; Heavy parallelization; Scalable ingestion; Immediate consistency; Time series and relational joins; Native InfluxDB line protocol; Grafana through Postgres wire support; Schema or schema-free; Aggregations and down sampling
Statistics
GitHub Stars
11.8K
GitHub Stars
16.3K
GitHub Forks
4.1K
GitHub Forks
1.5K
Stacks
129.6K
Stacks
19
Followers
108.6K
Followers
50
Votes
3.8K
Votes
17
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
  • 2
    Real-time analytics
  • 2
    Postgres wire protocol
  • 2
    SQL
  • 2
    No dependencies
  • 2
    Open source
Integrations
No integrations available
InfluxDB
InfluxDB
Java
Java
PostgreSQL
PostgreSQL

What are some alternatives to MySQL, QuestDB?

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