DBMS > Apache Phoenix vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Yaacomo

System Properties Comparison Apache Phoenix vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Globally distributed, horizontally scalable, multi-model database service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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.graphengine.io

azure.microsoft.com/services/cosmos-db

yaacomo.com

Technical documentation

phoenix.apache.org

www.graphengine.io/docs/manual

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Microsoft

Q2WEB GmbH

Initial release

2014

2010

2014

2009

Current release

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

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

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

.NET and C

Server operating systems

Linux
Unix
Windows

.NET

hosted

Android
Linux
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC

RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

user defined functions

yes

JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 can be defined down to the item level

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.