DBMS > Geode vs. GridGain vs. Memcached vs. SAP HANA

System Properties Comparison Geode vs. GridGain vs. Memcached vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

In-memory key-value store, originally intended for caching

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

geode.apache.org

www.gridgain.com

www.memcached.org

www.sap.com/products/hana.html

Technical documentation

geode.apache.org/docs

www.gridgain.com/docs/index.html

github.com/memcached/memcached/wiki

help.sap.com/hana

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

GridGain Systems, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Initial release

2002

2007

2003

2010

Current release

1.1, February 2017

GridGain 8.5.1

1.6.25, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

BSD license

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

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

SQL-like query language (OQL)

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

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

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

Proprietary protocol

JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

SQLScript, R

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

none

Repcached, a Memcached patch, provides this functionallity

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

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

Access rights per client and object definable

Security Hooks for custom implementations

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

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.