DBMS > Dgraph vs. EJDB vs. EsgynDB vs. Percona Server for MongoDB vs. Snowflake

System Properties Comparison Dgraph vs. EJDB vs. EsgynDB vs. Percona Server for MongoDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

dgraph.io

github.com/Softmotions/ejdb

www.esgyn.cn

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

Technical documentation

dgraph.io/docs

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

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Softmotions

Esgyn

Percona

Snowflake Computing Inc.

Initial release

2016

2012

2015

2014

Current release

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

Linux
OS X
Windows

server-less

Linux

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

in-process shared library

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

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

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

All languages supporting JDBC/ODBC/ADO.Net

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Multi-source replication between multi datacenters

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

In-memory capabilities

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

yes

via In-Memory Engine

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users and roles

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

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.