DBMS > Apache Phoenix vs. Citus vs. GeoSpock vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Phoenix vs. Citus vs. GeoSpock vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Spatial and temporal data processing engine for extreme data scale

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Time Series DBMS

Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

phoenix.apache.org

www.citusdata.com

geospock.com

azure.microsoft.com/services/cosmos-db

Technical documentation

phoenix.apache.org

docs.citusdata.com

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

GeoSpock

Microsoft

Initial release

2014

2010

2014

Current release

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

8.1, December 2018

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL, commercial license also 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

Java, Javascript

Server operating systems

Linux
Unix
Windows

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

standard, with numerous extensions

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

other methods possible by using 3rd party extensions

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

Access rights can be defined down to the item level

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.