DBMS > Google Cloud Datastore vs. GridGain vs. Kinetica vs. Realm vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. GridGain vs. Kinetica vs. Realm vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Fully vectorized database across both GPUs and CPUs

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cloud.google.com/datastore

Technical documentation

cloud.google.com/datastore/docs

www.gridgain.com/docs/index.html

docs.kinetica.com

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Google

GridGain Systems, Inc.

Kinetica

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2008

2007

2012

2014

Current release

GridGain 8.5.1

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

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++, .Net

C, C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

Android
Backend: server-less
iOS
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, details here

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 (GQL)

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

SQL-like DML and DDL statements

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

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

user defined functions

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

yes

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

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes (replicated cache)

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

GPU vRAM or System RAM

yes

In-Memory realm

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Security Hooks for custom implementations

Access rights for users and roles on table level

yes

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.