DBMS > EJDB vs. JaguarDB vs. MySQL vs. STSdb

System Properties Comparison EJDB vs. JaguarDB vs. MySQL vs. STSdb

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)

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

github.com/Softmotions/ejdb

www.jaguardb.com

www.mysql.com

github.com/STSSoft/STSdb4

Technical documentation

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

www.jaguardb.com/support.html

dev.mysql.com/doc

Developer

Softmotions

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

STS Soft SC

Initial release

2012

2015

1995

2011

Current release

3.3 July 2023

9.0.0, July 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL V3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

the server part. Clients available in other languages

C and C++

Server operating systems

server-less

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

primitive types and user defined types (classes)

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

in-process shared library

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C#
Java

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Multi-source replication
Source-replica 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

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

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

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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.