DBMS > Google Cloud Datastore vs. Greenplum vs. MaxDB vs. OrientDB vs. SAP HANA

System Properties Comparison Google Cloud Datastore vs. Greenplum vs. MaxDB vs. OrientDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A robust and reliable RDBMS optimized to run all major SAP solutions

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

cloud.google.com/datastore

greenplum.org

maxdb.sap.com

orientdb.org

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/datastore/docs

docs.greenplum.org

maxdb.sap.com/documentation

www.orientdb.com/docs/last/index.html

help.sap.com/hana

Developer

Google

Pivotal Software Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

OrientDB LTD; CallidusCloud; SAP

SAP

Initial release

2008

2005

1984

2010

Current release

7.0.0, September 2023

7.9.10.12, February 2024

3.2.29, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited community edition free

Open Source

Apache version 2

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

C++

Java

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

since Version 4.2

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language, no joins

yes

APIs and other access methods

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

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

C
Java
Perl
Python
R

.Net
C#
Java
Perl
PHP
Python

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

Server-side scripts

Stored procedures

using Google App Engine

yes

Java, Javascript

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

could be achieved with distributed queries

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

relationship in graphs

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)

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

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.