DBMS > EJDB vs. MySQL vs. Oracle vs. VoltDB

System Properties Comparison EJDB vs. MySQL vs. Oracle vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

Widely used RDBMS

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

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

github.com/Softmotions/ejdb

www.mysql.com

www.oracle.com/database

www.voltdb.com

Technical documentation

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

dev.mysql.com/doc

docs.oracle.com/en/database

docs.voltdb.com

Developer

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

VoltDB Inc.

Initial release

2012

1995

1980

2010

Current release

9.0.0, July 2024

23c, September 2023

11.3, April 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

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

Java, C++

Server operating systems

server-less

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X

for development

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

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.