DBMS > Google BigQuery vs. MySQL vs. QuestDB vs. STSdb

System Properties Comparison Google BigQuery vs. MySQL vs. QuestDB vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Widely used open source RDBMS

A high performance open source SQL database for time series data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	2.48
Rank	#115	Overall
	#9	Time Series DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

cloud.google.com/bigquery

www.mysql.com

questdb.io

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/bigquery/docs

dev.mysql.com/doc

questdb.io/docs

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

STS Soft SC

Initial release

2010

1995

2014

2011

Current release

8.3.0, January 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java (Zero-GC), C++, Rust

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Windows

Data scheme

yes

schema-free via InfluxDB Line Protocol

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL with time-series extensions

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

.NET Client API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

through memory mapped files

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 2024

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.