DBMS > Apache Phoenix vs. Google Cloud Datastore vs. Kdb vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Phoenix vs. Google Cloud Datastore vs. Kdb vs. Microsoft Azure Cosmos DB

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

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

High performance Time Series DBMS

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Time Series DBMS
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	7.71
Rank	#49	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

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

Website

phoenix.apache.org

cloud.google.com/datastore

kx.com

azure.microsoft.com/services/cosmos-db

Technical documentation

phoenix.apache.org

cloud.google.com/datastore/docs

code.kx.com

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Google

Kx Systems, a division of First Derivatives plc

Microsoft

Initial release

2014

2008

2000

kdb was released 2000, kdb+ in 2003

2014

Current release

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

3.6, May 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free 32-bit version

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

Server operating systems

Linux
Unix
Windows

hosted

Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

Secondary indexes

yes

table attribute 'grouped'

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like query language (q)

SQL-like query language

APIs and other access methods

JDBC

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

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

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
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

user defined functions

JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

with views

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

similar paradigm used for internal processing

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

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

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

rights management via user accounts

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.