DBMS > Geode vs. Google BigQuery vs. HarperDB vs. Kinetica

System Properties Comparison Geode vs. Google BigQuery vs. HarperDB vs. Kinetica

Please select another system to include it in the comparison.

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Fully vectorized database across both GPUs and CPUs

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.55
Rank	#252	Overall
	#38	Document stores

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Website

geode.apache.org

cloud.google.com/bigquery

www.harperdb.io

www.kinetica.com

Technical documentation

geode.apache.org/docs

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

docs.kinetica.com

Developer

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

Google

HarperDB

Kinetica

Initial release

2002

2010

2017

2012

Current release

1.1, February 2017

3.1, August 2021

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free community edition available

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

Node.js

C, C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
OS X

Linux

Data scheme

schema-free

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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 data manipulation statements

SQL-like DML and DDL statements

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC
RESTful HTTP API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Custom Functions

since release 3.1

user defined functions

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

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

the nodes on which a table resides can be defined

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

Foreign keys

Referential integrity

yes

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

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

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

Access rights for users and roles on table level

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.