DBMS > EJDB vs. jBASE vs. MySQL vs. YottaDB

System Properties Comparison EJDB vs. jBASE vs. MySQL vs. YottaDB

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)

A robust multi-value DBMS comprising development tools and middleware

Widely used open source RDBMS

A fast and solid embedded Key-value store

Primary database model

Document store

Multivalue DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

github.com/Softmotions/ejdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.mysql.com

yottadb.com

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

dev.mysql.com/doc

yottadb.com/resources/documentation

Developer

Softmotions

Rocket Software (formerly Zumasys)

Oracle

since 2010, originally MySQL AB, then Sun

YottaDB, LLC

Initial release

2012

1991

1995

2001

Current release

5.7

9.0.0, July 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.0

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

Server operating systems

server-less

AIX
Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

optional

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

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

by using the Octo plugin

APIs and other access methods

in-process shared library

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
Proprietary native API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

.Net
Basic
Jabbascript
Java

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

yes

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

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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

Access rights can be defined down to the item level

Users with fine-grained authorization concept

no user groups or roles

Users and groups based on OS-security mechanisms

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.