DBMS > ClickHouse vs. Kinetica vs. Riak KV vs. TDSQL for MySQL vs. Vitess

System Properties Comparison ClickHouse vs. Kinetica vs. Riak KV vs. TDSQL for MySQL vs. Vitess

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

Distributed, fault tolerant key-value store

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

clickhouse.com

www.kinetica.com

www.tencentcloud.com/products/dcdb

vitess.io

Technical documentation

clickhouse.com/docs

docs.kinetica.com

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

www.tencentcloud.com/document/product/1042

vitess.io/docs

Developer

Clickhouse Inc.

Kinetica

OpenSource, formerly Basho Technologies

Tencent

The Linux Foundation, PlanetScale

Initial release

2016

2012

2009

2013

Current release

v24.4.1.2088-stable, May 2024

7.1, August 2021

3.2.0, December 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

Apache Version 2.0, commercial licenses 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.

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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

C, C++

Erlang

Server operating systems

FreeBSD
Linux
macOS

Linux

Linux
OS X

hosted

Docker
Linux
macOS

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like DML and DDL statements

yes

with proprietary extensions

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

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

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++
Java
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

Server-side scripts

Stored procedures

yes

user defined functions

Erlang

yes

proprietary syntax

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

no "single point of failure"

Automatic sharding

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

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

yes, using Riak Security

Users with fine-grained authorization concept

no user groups or roles

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.