DBMS > Google Cloud Datastore vs. H2 vs. Riak TS vs. Yanza

System Properties Comparison Google Cloud Datastore vs. H2 vs. Riak TS vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Time Series DBMS for IoT Applications

Primary database model

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

cloud.google.com/datastore

www.h2database.com

yanza.com

Technical documentation

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Google

Thomas Mueller

Open Source, formerly Basho Technologies

Yanza

Initial release

2008

2005

2015

Current release

2.2.220, July 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

Server operating systems

hosted

All OS with a Java VM

Linux
OS X

Windows

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language (GQL)

yes

yes, limited

APIs and other access methods

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

JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

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

Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

any language that supports HTTP calls

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures and User-Defined Functions

Erlang

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

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 using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

selectable replication factor

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

links between datasets can be stored

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

yes, multi-version concurrency control (MVCC)

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page