DBMS > Google BigQuery vs. Hazelcast vs. Quasardb vs. TimescaleDB

System Properties Comparison Google BigQuery vs. Hazelcast vs. Quasardb 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

A widely adopted in-memory data grid

Distributed, high-performance timeseries database

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

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

cloud.google.com/bigquery

hazelcast.com

quasar.ai

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

doc.quasar.ai/master

docs.timescale.com

Developer

Google

Hazelcast

quasardb

Timescale

Initial release

2010

2008

2009

2017

Current release

5.3.6, November 2023

3.14.1, January 2024

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

hosted

All OS with a Java VM

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP API

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

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

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication with selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

Cryptographically strong user authentication and audit trail

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.