DBMS > Drizzle vs. RocksDB vs. SpatiaLite vs. TerarkDB

System Properties Comparison Drizzle vs. RocksDB vs. SpatiaLite vs. TerarkDB

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)

Spatial extension of SQLite

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Relational DBMS

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

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

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

rocksdb.org

www.gaia-gis.it/fossil/libspatialite/index

github.com/bytedance/terarkdb

Technical documentation

github.com/facebook/rocksdb/wiki

www.gaia-gis.it/gaia-sins/spatialite_topics.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Drizzle project, originally started by Brian Aker

Facebook, Inc.

Alessandro Furieri

ByteDance, originally Terark

Initial release

2008

2013

2008

2016

Current release

7.2.4, September 2012

8.11.4, April 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSD

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

restricted open source version available

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

Server operating systems

FreeBSD
Linux
OS X

Linux

server-less

Data scheme

yes

schema-free

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

with proprietary extensions

yes

APIs and other access methods

JDBC

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.