DBMS > Google Cloud Datastore vs. IBM Db2 vs. JaguarDB vs. SAP HANA

System Properties Comparison Google Cloud Datastore vs. IBM Db2 vs. JaguarDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

cloud.google.com/datastore

www.ibm.com/products/db2

www.jaguardb.com

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/datastore/docs

www.ibm.com/docs/en/db2

www.jaguardb.com/support.html

help.sap.com/hana

Developer

Google

IBM

DataJaguar, Inc.

SAP

Initial release

2008

1983

host version

2015

2010

Current release

12.1, October 2016

3.3 July 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free version is available

Open Source

GPL V3.0

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 and C++

C++

the server part. Clients available in other languages

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

Appliance or cloud-service

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
ODBC

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

using Google App Engine

yes

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

yes

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.

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

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

rights management via user accounts

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.