DBMS > Drizzle vs. RocksDB vs. Sequoiadb vs. Tarantool

System Properties Comparison Drizzle vs. RocksDB vs. Sequoiadb vs. Tarantool

Please select another system to include it in the comparison.

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.

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

NewSQL database with distributed OLTP and SQL

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Key-value store

Document store
Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

rocksdb.org

www.sequoiadb.com

www.tarantool.io

Technical documentation

github.com/facebook/rocksdb/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

www.tarantool.io/en/doc

Developer

Drizzle project, originally started by Brian Aker

Facebook, Inc.

Sequoiadb Ltd.

Initial release

2008

2013

2008

Current release

7.2.4, September 2012

9.2.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux

BSD
Linux
macOS

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with proprietary extensions

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

JDBC

C++ API
Java API

proprietary protocol using JSON

Open binary protocol

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

.Net
C++
Java
PHP
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

JavaScript

Lua, C and SQL stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Document is locked during a transaction

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.