DBMS > BaseX vs. Drizzle vs. EsgynDB vs. KeyDB

System Properties Comparison BaseX vs. Drizzle vs. EsgynDB vs. KeyDB

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

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Native XML DBMS

Relational DBMS

Key-value store

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Website

basex.org

www.esgyn.cn

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.basex.org

docs.keydb.dev

Developer

BaseX GmbH

Drizzle project, originally started by Brian Aker

Esgyn

EQ Alpha Technology Ltd.

Initial release

2007

2008

2015

2019

Current release

11.0, June 2024

7.2.4, September 2012

License

Commercial or Open Source

Open Source

BSD license

Open Source

GNU GPL

commercial

Open Source

BSD-3

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

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

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JDBC

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

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

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Lua

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

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
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

XML Injection Attacks: What to Know About XPath, XQuery, XXE & More
18 May 2022, Hashed Out by The SSL Store™

9 Skills You Need to Become a Data Engineer
2 November 2022, KDnuggets

Xml Databases Software Market Thriving at a Tremendous Growth – TIMC
16 June 2024, TIMC

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page