DBMS > EJDB vs. Microsoft Azure Cosmos DB vs. Prometheus vs. Quasardb vs. SAP Advantage Database Server

System Properties Comparison EJDB vs. Microsoft Azure Cosmos DB vs. Prometheus vs. Quasardb vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

Distributed, high-performance timeseries database

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

github.com/Softmotions/ejdb

azure.microsoft.com/services/cosmos-db

prometheus.io

quasar.ai

www.sap.com/products/advantage-database-server.html

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

doc.quasar.ai/master

Developer

Softmotions

Microsoft

quasardb

Sybase, SAP

Initial release

2012

2014

2015

2009

1993

Current release

3.14.1, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

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

Server operating systems

server-less

hosted

Linux
Windows

BSD
Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

Numeric data only

yes

integer and binary

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.

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

in-process shared library

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

RESTful HTTP/JSON API

HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Delphi
Perl
PHP

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

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

by Federation

Source-replica replication with selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

caching of (temporary) tables can be configured

User concepts

Access control

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

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.