DBMS > Geode vs. Google BigQuery vs. GridGain vs. Pinecone vs. STSdb

System Properties Comparison Geode vs. Google BigQuery vs. GridGain vs. Pinecone vs. STSdb

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

GridGain is an in-memory computing platform, built on Apache Ignite

A managed, cloud-native vector database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Relational DBMS

Key-value store
Relational DBMS

Vector DBMS

Key-value store

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	3.16
Rank	#95	Overall
	#2	Vector DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

geode.apache.org

cloud.google.com/bigquery

www.gridgain.com

www.pinecone.io

github.com/STSSoft/STSdb4

Technical documentation

geode.apache.org/docs

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

docs.pinecone.io/docs/overview

Developer

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

Google

GridGain Systems, Inc.

Pinecone Systems, Inc

STS Soft SC

Initial release

2002

2010

2007

2019

2011

Current release

1.1, February 2017

GridGain 8.5.1

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPLv2, commercial license available

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

Java, C++, .Net

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
OS X
Solaris
Windows

hosted

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

String, Number, Boolean

yes

primitive types and user defined types (classes)

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP API

.NET Client API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

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

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

Google Cloud Identity & Access Management (IAM)

Security Hooks for custom implementations

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.