DBMS > Drizzle vs. LeanXcale vs. LevelDB vs. RocksDB vs. Sqrrl

System Properties Comparison Drizzle vs. LeanXcale vs. LevelDB vs. RocksDB vs. Sqrrl

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

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

Website

www.leanxcale.com

github.com/google/leveldb

rocksdb.org

sqrrl.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

github.com/facebook/rocksdb/wiki

Developer

Drizzle project, originally started by Brian Aker

LeanXcale

Google

Facebook, Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2008

2015

2011

2013

2012

Current release

7.2.4, September 2012

1.23, February 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD

Open Source

BSD

commercial

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

Java

Server operating systems

FreeBSD
Linux
OS X

Illumos
Linux
OS X
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

with proprietary extensions

yes

through Apache Derby

APIs and other access methods

JDBC

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

C++ API
Java API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

C
C++
Java
PHP

C
Java
Scala

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++
Go
Java
Perl
Python
Ruby

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.