DBMS > Google Cloud Datastore vs. HBase vs. IBM Cloudant vs. Oracle vs. TigerGraph

System Properties Comparison Google Cloud Datastore vs. HBase vs. IBM Cloudant vs. Oracle vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

cloud.google.com/datastore

hbase.apache.org

www.ibm.com/products/cloudant

www.oracle.com/database

www.tigergraph.com

Technical documentation

cloud.google.com/datastore/docs

hbase.apache.org/book.html

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

docs.tigergraph.com

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

Initial release

2008

2010

1980

2017

Current release

2.3.4, January 2021

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

restricted free version is available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Erlang

C and C++

C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

Data scheme

schema-free

schema-free, schema definition possible

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes, details here

options to bring your own types, AVRO

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

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

Java API
RESTful HTTP API
Thrift

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++
Java

Server-side scripts

Stored procedures

using Google App Engine

yes

Coprocessors in Java

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

can be realized in PL/SQL

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.

Immediate Consistency or Eventual Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Single row ACID (across millions of columns)

atomic operations within a document possible

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Role-based access control

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.