DBMS > Dgraph vs. Ehcache vs. GridGain vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Dgraph vs. Ehcache vs. GridGain vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A widely adopted Java cache with tiered storage options

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

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Graph DBMS

Key-value store

Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

dgraph.io/docs

www.ehcache.org/documentation

www.gridgain.com/docs/index.html

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Dgraph Labs, Inc.

Terracotta Inc, owned by Software AG

GridGain Systems, Inc.

Facebook, Inc.

SAP

formerly Sybase

Initial release

2016

2009

2007

2013

1992

Current release

3.10.0, March 2022

GridGain 8.5.1

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

commercial

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

Java

Java, C++, .Net

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Solaris
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

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

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

yes

APIs and other access methods

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

JCache

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

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

Java

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

by using Terracotta Server

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

by using Terracotta Server

yes (replicated cache)

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.