DBMS > Geode vs. Riak KV vs. SAP HANA vs. Transwarp Hippo

System Properties Comparison Geode vs. Riak KV vs. SAP HANA vs. Transwarp Hippo

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

Distributed, fault tolerant key-value store

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

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Vector 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.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.05
Rank	#386	Overall
	#15	Vector DBMS

Website

geode.apache.org

www.sap.com/products/hana.html

www.transwarp.cn/en/subproduct/hippo

Technical documentation

geode.apache.org/docs

www.tiot.jp/riak-docs/riak/kv/latest

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.

OpenSource, formerly Basho Technologies

SAP

Initial release

2002

2009

2010

2023

Current release

1.1, February 2017

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X

Appliance or cloud-service

Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API
Native Erlang Interface

JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++
Java
Python

Server-side scripts

Stored procedures

user defined functions

Erlang

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

yes, using Riak Security

yes

Role based access control and fine grained access rights

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.