DBMS > Drizzle vs. EJDB vs. MaxDB vs. VoltDB

System Properties Comparison Drizzle vs. EJDB vs. MaxDB vs. VoltDB

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 document-store database library with JSON representation of queries (in MongoDB style)

A robust and reliable RDBMS optimized to run all major SAP solutions

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/Softmotions/ejdb

maxdb.sap.com

www.voltdb.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

maxdb.sap.com/documentation

docs.voltdb.com

Developer

Drizzle project, originally started by Brian Aker

Softmotions

SAP, acquired from Software AG (Adabas-D) in 1997

VoltDB Inc.

Initial release

2008

2012

1984

2010

Current release

7.2.4, September 2012

7.9.10.12, February 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPLv2

commercial

Limited community edition free

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Server operating systems

FreeBSD
Linux
OS X

server-less

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

only a subset of SQL 99

APIs and other access methods

JDBC

in-process shared library

ADO.NET
JDBC
ODBC
WebDAV

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C#
Java
Perl
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

SAP Content Server High Availability using Amazon EFS and SUSE | Amazon Web Services
30 December 2020, AWS Blog

SAP Aligns Mainstream Maintenance Commitments Across Its Enterprise Solutions
11 August 2020, SAP News

What is SAP S/4HANA?
21 March 2022, TechTarget

Alibaba Cloud Offers Access to SAP Software for Customers
5 June 2018, Alizila

Dear SAP, Why Don't You Make Hana A Success?
28 July 2021, E3-Magazin

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page