DBMS > Google Cloud Datastore vs. H2 vs. Warp 10 vs. YottaDB

System Properties Comparison Google Cloud Datastore vs. H2 vs. Warp 10 vs. YottaDB

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	7.57
Rank	#47	Overall
	#30	Relational DBMS

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

cloud.google.com/datastore

www.h2database.com

www.warp10.io

yottadb.com

Technical documentation

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

www.warp10.io/content/02_Getting_started

yottadb.com/resources/documentation

Developer

Google

Thomas Mueller

SenX

YottaDB, LLC

Initial release

2008

2005

2015

2001

Current release

2.2.220, July 2023

License

Commercial or Open Source

commercial

Open Source

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

Open Source

Apache License 2.0

Open Source

AGPL 3.0

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

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

Docker
Linux

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

by using the Octo plugin

APIs and other access methods

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

JDBC
ODBC

HTTP API
Jupyter
WebSocket

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

Java

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures and User-Defined Functions

yes

WarpScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

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

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

based on HBase

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

optimistic locking

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

Users and groups based on OS-security mechanisms

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 vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

provided by Google News

Launched Just A Year Ago, Open-Source Scality S3 Server Gains Extraordinary Momentum As It Simplifies The Life Of Developers
28 June 2017, PR Newswire

provided by Google News

Share this page