DBMS > Dolt vs. Quasardb vs. Riak KV vs. RocksDB

System Properties Comparison Dolt vs. Quasardb vs. Riak KV 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

Distributed, high-performance timeseries database

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

Key-value store

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

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

quasar.ai

rocksdb.org

Technical documentation

docs.dolthub.com

doc.quasar.ai/master

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

github.com/facebook/rocksdb/wiki

Developer

DoltHub Inc

quasardb

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2018

2009

2013

Current release

3.14.1, January 2024

3.2.0, December 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

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

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

Linux
macOS
Windows

BSD
Linux
OS X
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

restricted

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

CLI Client
HTTP REST

HTTP API

HTTP API
Native Erlang Interface

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

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

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++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Sharding

no "single point of failure"

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.

Source-replica replication with selectable replication factor

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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

yes

User concepts

Access control

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

Cryptographically strong user authentication and audit trail

yes, using Riak Security

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.