DBMS > Geode vs. Google BigQuery vs. Kinetica vs. SpaceTime vs. VoltDB

System Properties Comparison Geode vs. Google BigQuery vs. Kinetica vs. SpaceTime vs. VoltDB

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

Large scale data warehouse service with append-only tables

Fully vectorized database across both GPUs and CPUs

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Relational DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

geode.apache.org

cloud.google.com/bigquery

www.kinetica.com

www.mireo.com/spacetime

www.voltdb.com

Technical documentation

geode.apache.org/docs

cloud.google.com/bigquery/docs

docs.kinetica.com

docs.voltdb.com

Developer

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

Google

Kinetica

Mireo

VoltDB Inc.

Initial release

2002

2010

2012

2020

2010

Current release

1.1, February 2017

7.1, August 2021

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux

Linux
OS X

for development

Data scheme

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

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

yes

only a subset of SQL 99

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

C#
C++
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Java

Triggers

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Fixed-grid hypercubes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

Real-time block device replication (DRBD)

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes, on a single node

Since BigQuery is designed for querying data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

User concepts

Access control

Access rights per client and object definable

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles on table level

yes

Users and roles with access to stored procedures

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.