DBMS > ClickHouse vs. Kinetica vs. Riak TS vs. SAP SQL Anywhere vs. VoltDB

System Properties Comparison ClickHouse vs. Kinetica vs. Riak TS vs. SAP SQL Anywhere vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS
Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

clickhouse.com

www.kinetica.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.voltdb.com

Technical documentation

clickhouse.com/docs

docs.kinetica.com

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

help.sap.com/docs/SAP_SQL_Anywhere

docs.voltdb.com

Developer

Clickhouse Inc.

Kinetica

Open Source, formerly Basho Technologies

SAP

formerly Sybase

VoltDB Inc.

Initial release

2016

2012

2015

1992

2010

Current release

v24.4.2.141-stable, June 2024

7.1, August 2021

3.0.0, September 2022

17, July 2015

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

C++

C, C++

Erlang

Java, C++

Server operating systems

FreeBSD
Linux
macOS

Linux

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

restricted

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like DML and DDL statements

yes, limited

yes

only a subset of SQL 99

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

ADO.NET
HTTP API
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

Erlang

yes, in C/C++, Java, .Net or Perl

Java

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

key based and custom

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Source-replica replication

selectable replication factor

Source-replica replication

Database mirroring

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.