DBMS > Geode vs. HyperSQL vs. KairosDB vs. SAP HANA vs. Valentina Server

System Properties Comparison Geode vs. HyperSQL vs. KairosDB vs. SAP HANA vs. Valentina Server

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Distributed Time Series DBMS based on Cassandra or H2

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

Object-relational database and reports server

Primary database model

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.51
Rank	#147	Overall
	#25	Key-value stores

Score	3.14
Rank	#85	Overall
	#46	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Website

geode.apache.org

hsqldb.org

github.com/kairosdb/kairosdb

www.sap.com/products/hana.html

www.valentina-db.net

Technical documentation

geode.apache.org/docs

hsqldb.org/web/hsqlDocsFrame.html

kairosdb.github.io

help.sap.com/hana

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

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

SAP

Paradigma Software

Initial release

2002

2001

2013

2010

1999

Current release

1.1, February 2017

2.7.2, June 2023

1.2.2, November 2018

2.0 SPS07 (April 4, 2023), April 2023

5.7.5

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

based on BSD license

Open Source

Apache 2.0

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux
OS X
Windows

Appliance or cloud-service

Linux
OS X
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.

Secondary indexes

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

JDBC via HTTP
JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC

ODBC

Supported programming languages

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

All languages supporting JDBC/ODBC
Java

Java
JavaScript

Node.js
PHP
Python

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

Java, SQL

SQLScript, R

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

fine grained access rights according to SQL-standard

simple password-based access control

yes

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.