DBMS > Google BigQuery vs. Heroic vs. mSQL vs. TimescaleDB

System Properties Comparison Google BigQuery vs. Heroic vs. mSQL vs. TimescaleDB

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

mSQL (Mini SQL) is a simple and lightweight RDBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

cloud.google.com/bigquery

github.com/spotify/heroic

hughestech.com.au/products/msql

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

docs.timescale.com

Developer

Google

Spotify

Hughes Technologies

Timescale

Initial release

2010

2014

1994

2017

Current release

4.4, October 2021

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free licenses can be provided

Open Source

Apache 2.0

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.

Implementation language

Java

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

via Elasticsearch

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

More information provided by the system vendor

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.