DBMS > Google Cloud Datastore vs. Graph Engine vs. SAP HANA vs. Spark SQL vs. Transbase

System Properties Comparison Google Cloud Datastore vs. Graph Engine vs. SAP HANA vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Graph DBMS
Key-value store

Relational DBMS

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.47
Rank	#76	Overall
	#12	Document stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/datastore

www.graphengine.io

www.sap.com/products/hana.html

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/datastore/docs

www.graphengine.io/docs/manual

help.sap.com/hana

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

Microsoft

SAP

Apache Software Foundation

Transaction Software GmbH

Initial release

2008

2010

2014

1987

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

Apache 2.0

commercial

free development license

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

.NET and C

Scala

C and C++

Server operating systems

hosted

.NET

Appliance or cloud-service

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C#
C++
F#
Visual Basic

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

SQLScript, R

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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)

yes

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.