DBMS > EJDB vs. Microsoft SQL Server vs. Newts vs. Prometheus vs. Quasardb

System Properties Comparison EJDB vs. Microsoft SQL Server vs. Newts vs. Prometheus vs. Quasardb

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

Time Series DBMS based on Cassandra

Open-source Time Series DBMS and monitoring system

Distributed, high-performance timeseries database

Primary database model

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

www.microsoft.com/en-us/sql-server

opennms.github.io/newts

prometheus.io

quasar.ai

Technical documentation

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

learn.microsoft.com/en-US/sql/sql-server

github.com/OpenNMS/newts/wiki

prometheus.io/docs

doc.quasar.ai/master

Developer

Softmotions

Microsoft

OpenNMS Group

quasardb

Initial release

2012

1989

2014

2015

2009

Current release

SQL Server 2022, November 2022

3.14.1, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

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

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

Java

C++

Server operating systems

server-less

Linux
Windows

Linux
OS X
Windows

Linux
Windows

BSD
Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numeric data only

yes

integer and binary

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

Import of XML data possible

Secondary indexes

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST
Java API

RESTful HTTP/JSON API

HTTP API

Supported programming languages

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java

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

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

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

based on Cassandra

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

selectable replication factor

based on Cassandra

yes

by Federation

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.