DBMS > Apache Phoenix vs. GeoMesa vs. Google BigQuery vs. IBM Cloudant

System Properties Comparison Apache Phoenix vs. GeoMesa vs. Google BigQuery vs. IBM Cloudant

Please select another system to include it in the comparison.

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.

Large scale data warehouse service with append-only tables

Database as a Service offering based on Apache CouchDB

Primary database model

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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Website

phoenix.apache.org

www.geomesa.org

cloud.google.com/bigquery

www.ibm.com/products/cloudant

Technical documentation

phoenix.apache.org

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

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

Developer

Apache Software Foundation

CCRi and others

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2014

2010

Current release

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

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

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

Scala

Erlang

Server operating systems

Linux
Unix
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users can be defined per database

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.