DBMS > Dgraph vs. EsgynDB vs. GridGain vs. Percona Server for MongoDB vs. RocksDB

System Properties Comparison Dgraph vs. EsgynDB vs. GridGain vs. Percona Server for MongoDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

GridGain is an in-memory computing platform, built on Apache Ignite

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Graph DBMS

Relational DBMS

Key-value store
Relational DBMS

Document store

Key-value store

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

dgraph.io

www.esgyn.cn

www.gridgain.com

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

rocksdb.org

Technical documentation

dgraph.io/docs

www.gridgain.com/docs/index.html

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

github.com/facebook/rocksdb/wiki

Developer

Dgraph Labs, Inc.

Esgyn

GridGain Systems, Inc.

Percona

Facebook, Inc.

Initial release

2016

2015

2007

2015

2013

Current release

GridGain 8.5.1

3.4.10-2.10, November 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL Version 2

Open Source

BSD

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

Java, C++, .Net

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

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

ADO.NET
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol using JSON

C++ API
Java API

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

Access rights for users and roles

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.