DBMS > Google Cloud Datastore vs. Microsoft Azure Table Storage vs. SAP HANA vs. STSdb vs. UniData,UniVerse

System Properties Comparison Google Cloud Datastore vs. Microsoft Azure Table Storage vs. SAP HANA vs. STSdb vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

In-memory, column based data store. Available as appliance or cloud service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	6.45
Rank	#67	Overall
	#12	Document stores

Score	5.53
Rank	#77	Overall
	#5	Wide column stores

Score	54.96
Rank	#21	Overall
	#13	Relational DBMS

Score	0.00
Rank	#357	Overall
	#56	Key-value stores

Score	4.44
Rank	#85	Overall
	#2	Multivalue DBMS

Website

cloud.google.com/datastore

azure.microsoft.com/en-us/services/storage/tables

www.sap.com/products/hana.html

github.com/STSSoft/STSdb4

www.rocketsoftware.com/products/rocket-u2

Technical documentation

cloud.google.com/datastore/docs

help.sap.com/hana

www.rocketsoftware.com/products/rocket-u2/documentation

Developer

Google

Microsoft

SAP

STS Soft SC

Rocket Software

Initial release

2008

2012

2010

2011

1985

Current release

2.0 SPS05 (June 26, 2020), June 2020

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

hosted

Appliance or cloud-service

Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

optional

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

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC

.NET Client API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

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

C#
Java

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

using Google App Engine

SQLScript, R

yes

Triggers

Callbacks using the Google Apps Engine

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

none

Source-replica replication

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

optimistic locking

ACID

configurable

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

Access rights based on private key authentication or shared access signatures

yes

Access rights according to SQL-standard and operating system based

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.