DBMS > EJDB vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. RavenDB

System Properties Comparison EJDB vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. RavenDB

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

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store

Key-value store
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series 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	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.68
Rank	#102	Overall
	#19	Document stores

Website

github.com/Softmotions/ejdb

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

ravendb.net

Technical documentation

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

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

Developer

Softmotions

DataJaguar, Inc.

Microsoft

Hibernating Rhinos

Initial release

2012

2015

2014

2010

Current release

3.3 July 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL V3.0

commercial

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

server-less

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

in-process shared library

JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP 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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

User concepts

Access control

rights management via user accounts

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.