DBMS > Google Cloud Datastore vs. HBase vs. Kinetica vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. HBase vs. Kinetica vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Document store

Wide column 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.49
Rank	#79	Overall
	#12	Document stores

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

cloud.google.com/datastore

hbase.apache.org

www.kinetica.com

www.snowflake.com

Technical documentation

cloud.google.com/datastore/docs

hbase.apache.org/book.html

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Kinetica

Snowflake Computing Inc.

Initial release

2008

2012

2014

Current release

2.3.4, January 2021

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Linux

hosted

Data scheme

schema-free

schema-free, schema definition possible

yes

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

Typing

predefined data types such as float or date

yes, details here

options to bring your own types, AVRO

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)

SQL-like DML and DDL statements

yes

APIs and other access methods

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

Java API
RESTful HTTP API
Thrift

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

Coprocessors in Java

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

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

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

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 or Eventual 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

Single row ACID (across millions of columns)

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

User concepts

Access control

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights for users and roles on table level

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.