DBMS > EJDB vs. OrientDB vs. Prometheus vs. Snowflake vs. TigerGraph

System Properties Comparison EJDB vs. OrientDB vs. Prometheus vs. Snowflake vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

Multi-model DBMS (Document, Graph, Key/Value)

Open-source Time Series DBMS and monitoring system

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store

Document store
Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

Graph DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

github.com/Softmotions/ejdb

Technical documentation

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

www.orientdb.com/docs/last/index.html

prometheus.io/docs

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Softmotions

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2012

2010

2015

2014

2017

Current release

3.2.29, March 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache version 2

Open Source

Apache 2.0

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

Java

C++

Server operating systems

server-less

All OS with a Java JDK (>= JDK 6)

Linux
Windows

hosted

Linux

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numeric data only

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-like query language (GSQL)

APIs and other access methods

in-process shared library

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

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

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

Java, Javascript

user defined functions

yes

Triggers

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

relationship in graphs

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

In-memory capabilities

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

User concepts

Access control

Access rights for users and roles; record level security configurable

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.