DBMS > EsgynDB vs. Greenplum vs. GridGain vs. InterSystems Caché vs. RocksDB

System Properties Comparison EsgynDB vs. Greenplum vs. GridGain vs. InterSystems Caché vs. RocksDB

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

A multi-model DBMS and application server

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

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Document store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

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

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

Website

www.esgyn.cn

greenplum.org

www.gridgain.com

www.intersystems.com/products/cache

rocksdb.org

Technical documentation

docs.greenplum.org

www.gridgain.com/docs/index.html

docs.intersystems.com

github.com/facebook/rocksdb/wiki

Developer

Esgyn

Pivotal Software Inc.

GridGain Systems, Inc.

InterSystems

Facebook, Inc.

Initial release

2015

2005

2007

1997

2013

Current release

7.0.0, September 2023

GridGain 8.5.1

2018.1.4, May 2020

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

Linux
OS X
Solaris
Windows

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

depending on used data model

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

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

yes

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

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

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

.NET Client API
JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
Java
Perl
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

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

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

Access rights for users, groups 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.