DBMS > Geode vs. OpenQM vs. SingleStore vs. Snowflake vs. XTDB

System Properties Comparison Geode vs. OpenQM vs. SingleStore vs. Snowflake vs. XTDB

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

geode.apache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.singlestore.com

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

geode.apache.org/docs

docs.singlestore.com

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

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

Rocket Software, originally Martin Phillips

SingleStore Inc.

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2002

1993

2013

2014

2019

Current release

1.1, February 2017

3.4-12

8.5, January 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPLv2, extended commercial license available

commercial

free developer edition available

commercial

Open Source

MIT License

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++, Go

Clojure

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

64 bit version required

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

with some exceptions

yes

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

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

but no triggers and foreign keys

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

Bash
C
C#
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

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

yes

Sharding

hash partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights can be defined down to the item level

Fine grained access control via users, groups and roles

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.