DBMS > Geode vs. HyperSQL vs. JaguarDB vs. SAP IQ vs. Snowflake

System Properties Comparison Geode vs. HyperSQL vs. JaguarDB vs. SAP IQ vs. Snowflake

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

Performant, highly scalable DBMS for AI and IoT applications

Columnar RDBMS optimized for Big Data analytics

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

column-oriented

Relational DBMS

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

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

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geode.apache.org

hsqldb.org

www.jaguardb.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

Technical documentation

geode.apache.org/docs

hsqldb.org/web/hsqlDocsFrame.html

www.jaguardb.com/support.html

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

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

DataJaguar, Inc.

SAP, formerly Sybase

Snowflake Computing Inc.

Initial release

2002

2001

2015

1994

2014

Current release

1.1, February 2017

2.7.2, June 2023

3.3 July 2023

16.1 SPS04, April 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

based on BSD license

Open Source

GPL V3.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

the server part. Clients available in other languages

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

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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)

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

All languages supporting JDBC/ODBC
Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java, SQL

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

SAP/Sybase Replication Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

fine grained access rights according to SQL-standard

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.