DBMS > BigchainDB vs. Drizzle vs. Geode vs. SQLite vs. WakandaDB

System Properties Comparison BigchainDB vs. Drizzle vs. Geode vs. SQLite vs. WakandaDB

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Widely used embeddable, in-process RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

www.sqlite.org/docs.html

wakanda.github.io/doc

Developer

Drizzle project, originally started by Brian Aker

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Dwayne Richard Hipp

Wakanda SAS

Initial release

2016

2008

2002

2000

2012

Current release

7.2.4, September 2012

1.1, February 2017

3.46.0 (23 May 2024), May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Public Domain

Open Source

AGPLv3, extended commercial license 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

Python

C++

Java

C++, JavaScript

Server operating systems

Linux

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Java
PHP

.Net
All JVM based languages
C++
Groovy
Java
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

JavaScript

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

yes

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.