DBMS > Geode vs. gStore vs. HyperSQL vs. TimesTen vs. Yanza

System Properties Comparison Geode vs. gStore vs. HyperSQL vs. TimesTen vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A native Graph DBMS to store and maintain very large RDF datasets.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

In-Memory RDBMS compatible to Oracle

Time Series DBMS for IoT Applications

Primary database model

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

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

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

geode.apache.org

en.gstore.cn

hsqldb.org

www.oracle.com/database/technologies/related/timesten.html

yanza.com

Technical documentation

geode.apache.org/docs

en.gstore.cn/#/enDocs

hsqldb.org/web/hsqlDocsFrame.html

docs.oracle.com/database/timesten-18.1

Developer

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

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Yanza

Initial release

2002

2016

2001

1998

2015

Current release

1.1, February 2017

1.2, November 2023

2.7.2, June 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD

Open Source

based on BSD license

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

All OS with a Java VM

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

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Windows

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

yes

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.

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
SPARQL 1.1

HTTP API

JDBC via HTTP
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC
Java

C
C++
Java
PL/SQL

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

Java, SQL

PL/SQL

Triggers

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Users, roles and permissions, Role-Based Access Control (RBAC) supported

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

provided by Google News

HyperSQL DataBase flaw leaves library vulnerable to RCE
24 October 2022, The Daily Swig

Introduction to JDBC with HSQLDB tutorial
14 November 2022, TheServerSide.com

provided by Google News

Share this page