DBMS > EJDB vs. Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. TinkerGraph

System Properties Comparison EJDB vs. Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Graph 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	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

github.com/Softmotions/ejdb

azure.microsoft.com/en-us/products/azure-sql/database

nsdb.io

origodb.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

docs.microsoft.com/en-us/azure/azure-sql

nsdb.io/Architecture

origodb.com/docs

Developer

Softmotions

Microsoft

Robert Friberg et al

Initial release

2012

2010

2017

2009

under the name LiveDB

2009

Current release

V12

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Java, Scala

Java

Server operating systems

server-less

hosted

Linux
macOS

Linux
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

yes: int, bigint, decimal, string

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

TinkerPop 3

Supported programming languages

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

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

Java
Scala

.Net

Groovy
Java

Server-side scripts

Stored procedures

Transact SQL

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

yes

Relationships in graphs

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

Using Apache Lucene

yes

Write ahead log

optional

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

PostgreSQL is the DBMS of the Year 2020
4 January 2021, Paul Andlinger, Matthias Gelbmann

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

The popularity of cloud-based DBMSs has increased tenfold in four years
7 February 2017, Matthias Gelbmann

show all

Recent citations in the news

Public Preview: New Azure SQL Database skills introduced to Microsoft Copilot in Azure | Azure updates
21 May 2024, Microsoft

Copilot in Azure SQL Database in Private Preview
27 March 2024, InfoQ.com

Microsoft unveils Copilot for Azure SQL Database
27 March 2024, InfoWorld

Azure SQL Database migration to OCI - resources estimation and migration approach
11 January 2024, blogs.oracle.com

Azure SQL Database takes Saturday off on US east coast following network power failure
18 September 2023, The Register

provided by Google News

Why developers like Apache TinkerPop, an open source framework for graph computing | Amazon Web Services
27 September 2021, AWS Blog

Introducing Gremlin query hints for Amazon Neptune
26 February 2019, AWS Blog

InfiniteGraph Gets Support for Common Graph Database Language and More
21 February 2012, SiliconANGLE News

provided by Google News

Share this page