DBMS > BaseX vs. Drizzle vs. LeanXcale vs. Percona Server for MongoDB vs. RocksDB

System Properties Comparison BaseX vs. Drizzle vs. LeanXcale vs. Percona Server for MongoDB vs. RocksDB

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Native XML DBMS

Relational DBMS

Key-value store
Relational DBMS

Document store

Key-value store

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

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

Score	0.52
Rank	#254	Overall
	#39	Document stores

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

Website

basex.org

www.leanxcale.com

www.percona.com/mongodb/software/percona-server-for-mongodb

rocksdb.org

Technical documentation

docs.basex.org

docs.percona.com/percona-distribution-for-mongodb

github.com/facebook/rocksdb/wiki

Developer

BaseX GmbH

Drizzle project, originally started by Brian Aker

LeanXcale

Percona

Facebook, Inc.

Initial release

2007

2008

2015

2013

Current release

10.7, August 2023

7.2.4, September 2012

3.4.10-2.10, November 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

BSD license

Open Source

GNU GPL

commercial

Open Source

GPL Version 2

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

Java

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JDBC

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

proprietary protocol using JSON

C++ API
Java API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

C
C++
Java
PHP

C
Java
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

via events

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

ACID

yes

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

via In-Memory Engine

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for 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.