DBMS > Dolt vs. HEAVY.AI vs. Kinetica vs. RocksDB

System Properties Comparison Dolt vs. HEAVY.AI vs. Kinetica vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/dolthub/dolt
www.dolthub.com

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

rocksdb.org

Technical documentation

docs.dolthub.com

docs.heavy.ai

docs.kinetica.com

github.com/facebook/rocksdb/wiki

Developer

DoltHub Inc

HEAVY.AI, Inc.

Kinetica

Facebook, Inc.

Initial release

2018

2016

2012

2013

Current release

5.10, January 2022

7.1, August 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

BSD

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.

Implementation language

C++ and CUDA

C, C++

C++

Server operating systems

Linux
macOS
Windows

Linux

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

CLI Client
HTTP REST

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

yes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.