DBMS > Google Cloud Datastore vs. OpenQM vs. Postgres-XL vs. Tigris

System Properties Comparison Google Cloud Datastore vs. OpenQM vs. Postgres-XL vs. Tigris

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store

Multivalue DBMS

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

cloud.google.com/datastore

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.postgres-xl.org

www.tigrisdata.com

Technical documentation

cloud.google.com/datastore/docs

www.postgres-xl.org/documentation

www.tigrisdata.com/docs

Developer

Google

Rocket Software, originally Martin Phillips

Tigris Data, Inc.

Initial release

2008

1993

2014

since 2012, originally named StormDB

2022

Current release

3.4-12

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Mozilla public license

Open Source

Apache Version 2.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

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
macOS

Linux
macOS
Windows

Data scheme

schema-free

yes

with some exceptions

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

distributed, parallel query execution

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

using Google App Engine

yes

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

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

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

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Access rights for users and roles

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

Best cloud storage of 2024
21 May 2024, TechRadar

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

Google Cloud is NOT magicking away data egress fees
12 January 2024, The Stack

Why Google is waiving egress fees for disgruntled customers ditching GCP
11 January 2024, The Register

provided by Google News

Tigris Data Unveils Beta Launch of New Vector Search Tool
19 May 2023, Datanami

Tigris Data Launches All-in-One Developer Data Platform
27 September 2022, Datanami

FerretDB Provides Alternative to MongoDB
19 May 2023, Datanami

Latest Asigra platform targets SaaS backup for MSPs
6 March 2023, TechTarget

provided by Google News

Share this page