DBMS > Google BigQuery vs. Google Cloud Datastore vs. Hyprcubd vs. OpenQM vs. SAP SQL Anywhere

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. Hyprcubd vs. OpenQM vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Large scale data warehouse service with append-only tables

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

Serverless Time Series DBMS

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Website

cloud.google.com/bigquery

cloud.google.com/datastore

hyprcubd.com (offline)

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

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Google

Hyprcubd, Inc.

Rocket Software, originally Martin Phillips

SAP

formerly Sybase

Initial release

2010

2008

1993

1992

Current release

3.4-12

17, July 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

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

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

time, int, uint, float, string

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

yes

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

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

gRPC (https)

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
Basic
C
Java
Objective C
PHP
Python

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

yes

yes, in C/C++, Java, .Net or Perl

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Source-replica replication

Database mirroring

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

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.

Eventual Consistency

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

Since BigQuery is designed for querying 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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

token access

Access rights can be defined down to the item level

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.