DBMS > Google Cloud Datastore vs. Heroic vs. OpenEdge vs. Riak TS vs. SAP HANA

System Properties Comparison Google Cloud Datastore vs. Heroic vs. OpenEdge vs. Riak TS vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Application development environment with integrated database management system

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

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

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

cloud.google.com/datastore

github.com/spotify/heroic

www.progress.com/openedge

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/datastore/docs

spotify.github.io/heroic

documentation.progress.com/output/ua/OpenEdge_latest

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

help.sap.com/hana

Developer

Google

Spotify

Progress Software Corporation

Open Source, formerly Basho Technologies

SAP

Initial release

2008

2014

1984

2015

2010

Current release

OpenEdge 12.2, March 2020

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

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

Java

Erlang

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

restricted

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

close to SQL 92

yes, limited

yes

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

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

Progress proprietary ABL (Advanced Business Language)

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

Server-side scripts

Stored procedures

using Google App Engine

yes

Erlang

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Source-replica replication

selectable replication factor

yes

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.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

links between datasets can be stored

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

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)

Users and groups

yes

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.