DBMS > Citus vs. Google BigQuery vs. Kinetica vs. Riak TS vs. TimescaleDB

System Properties Comparison Citus vs. Google BigQuery vs. Kinetica vs. Riak TS vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Large scale data warehouse service with append-only tables

Fully vectorized database across both GPUs and CPUs

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store

Spatial DBMS
Time Series DBMS

Relational DBMS

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.citusdata.com

cloud.google.com/bigquery

www.kinetica.com

www.timescale.com

Technical documentation

docs.citusdata.com

cloud.google.com/bigquery/docs

docs.kinetica.com

www.tiot.jp/riak-docs/riak/ts/latest

docs.timescale.com

Developer

Google

Kinetica

Open Source, formerly Basho Technologies

Timescale

Initial release

2010

2012

2015

2017

Current release

8.1, December 2018

7.1, August 2021

3.0.0, September 2022

2.15.0, May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

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

C, C++

Erlang

Server operating systems

Linux

hosted

Linux

Linux
OS X

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

SQL-like DML and DDL statements

yes, limited

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

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

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

in JavaScript

user defined functions

Erlang

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

triggers when inserted values for one or more columns fall within a specified range

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

Source-replica replication

selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

Transaction concepts

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

ACID

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.

yes

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles on table level

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.