DBMS > Apache Phoenix vs. GeoMesa vs. IBM Cloudant vs. Microsoft Azure Table Storage vs. Oracle

System Properties Comparison Apache Phoenix vs. GeoMesa vs. IBM Cloudant vs. Microsoft Azure Table Storage vs. Oracle

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Database as a Service offering based on Apache CouchDB

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used RDBMS

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	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

phoenix.apache.org

www.geomesa.org

www.ibm.com/products/cloudant

azure.microsoft.com/en-us/services/storage/tables

www.oracle.com/database

Technical documentation

phoenix.apache.org

www.geomesa.org/documentation/stable/user/index.html

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

Developer

Apache Software Foundation

CCRi and others

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Oracle

Initial release

2014

2010

2012

1980

Current release

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

4.0.5, February 2024

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 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

Scala

Erlang

C and C++

Server operating systems

Linux
Unix
Windows

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

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

with proprietary extensions

APIs and other access methods

JDBC

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
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

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

Multi-source replication
Source-replica replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

depending on storage layer

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

optimistic locking

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

depending on storage layer

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

depending on the DBMS used for storage

Access rights for users can be defined per database

Access rights based on private key authentication or shared access signatures

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.