DBMS > Apache Phoenix vs. GBase vs. Google Cloud Datastore vs. IBM Cloudant vs. Oracle

System Properties Comparison Apache Phoenix vs. GBase vs. Google Cloud Datastore vs. IBM Cloudant vs. Oracle

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

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	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

phoenix.apache.org

www.gbase.cn

cloud.google.com/datastore

www.ibm.com/products/cloudant

www.oracle.com/database

Technical documentation

phoenix.apache.org

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

Developer

Apache Software Foundation

General Data Technology Co., Ltd.

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

Initial release

2014

2004

2008

2010

1980

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

GBase 8a, GBase 8s, GBase 8c

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

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

C, Java, Python

Erlang

C and C++

Server operating systems

Linux
Unix
Windows

Linux

hosted

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

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

Standard with numerous extensions

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
C API
JDBC
ODBC

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

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

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

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

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

atomic operations within a document possible

ACID

isolation level can be parameterized

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

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

Access rights for users can be defined per database

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.