DBMS > Drizzle vs. mSQL vs. RocksDB vs. Rockset vs. VoltDB

System Properties Comparison Drizzle vs. mSQL vs. RocksDB vs. Rockset vs. VoltDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Secondary database models

Relational DBMS
Search engine

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

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

hughestech.com.au/products/msql

rocksdb.org

rockset.com

www.voltdb.com

Technical documentation

github.com/facebook/rocksdb/wiki

docs.rockset.com

docs.voltdb.com

Developer

Drizzle project, originally started by Brian Aker

Hughes Technologies

Facebook, Inc.

Rockset

VoltDB Inc.

Initial release

2008

1994

2013

2019

2010

Current release

7.2.4, September 2012

4.4, October 2021

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free licenses can be provided

Open Source

BSD

commercial

Open Source

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

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

Java, C++

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux

hosted

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

Read-only SQL queries, including JOINs

yes

only a subset of SQL 99

APIs and other access methods

JDBC

JDBC
ODBC

C++ API
Java API

HTTP REST

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

C
C++
Delphi
Java
Perl
PHP
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users and organizations can be defined via Rockset console

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.