DBMS > EsgynDB vs. Hazelcast vs. JanusGraph vs. MariaDB vs. Oracle Berkeley DB

System Properties Comparison EsgynDB vs. Hazelcast vs. JanusGraph vs. MariaDB vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Widely used in-process key-value store

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

hazelcast.org/imdg/docs

docs.janusgraph.org

mariadb.com/kb/en/library

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Esgyn

Hazelcast

Linux Foundation; originally developed as Titan by Aurelius

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2015

2008

2017

2009

Fork of MySQL, which was first released in 1995

1994

Current release

5.3.6, November 2023

0.6.3, February 2023

11.3.2, February 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

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

C++, Java

Java

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Unix
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

yes

Dynamic columns are supported

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.

yes

the object must implement a serialization strategy

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Clojure
Java
Python

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Event Listeners, Executor Services

yes

PL/SQL compatibility added with version 10.3

Triggers

yes

Events

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

several options for horizontal partitioning and Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Replicated Map

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

not for in-memory storage engine

yes

In-memory capabilities

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

yes

with MEMORY storage engine

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.