DBMS > Apache Phoenix vs. Atos Standard Common Repository vs. Graph Engine vs. Postgres-XL

System Properties Comparison Apache Phoenix vs. Atos Standard Common Repository vs. Graph Engine vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

phoenix.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.graphengine.io

www.postgres-xl.org

Technical documentation

phoenix.apache.org

www.graphengine.io/docs/manual

www.postgres-xl.org/documentation

Developer

Apache Software Foundation

Atos Convergence Creators

Microsoft

Initial release

2014

2016

2010

2014

since 2012, originally named StormDB

Current release

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

1703

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Open Source

Mozilla public license

Cloud-based only

Only available as a cloud service

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

Linux

.NET

Linux
macOS

Data scheme

yes

late-bound, schema-on-read capabilities

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

JDBC

LDAP

RESTful HTTP API

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

Supported programming languages

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

All languages with LDAP bindings

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

MVCC

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

LDAP bind authentication

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

show all

Recent citations in the news

Supercharge SQL on Your Data in Apache HBase with Apache Phoenix | Amazon Web Services
2 June 2016, AWS Blog

Azure #HDInsight Apache Phoenix now supports Zeppelin
16 August 2018, Microsoft

Bridge the SQL-NoSQL gap with Apache Phoenix
4 February 2016, InfoWorld

Apache Calcite, FreeMarker, Gora, Phoenix, and Solr updated
27 March 2017, SDTimes.com

Azure HDInsight Analytics Platform Now Supports Apache Hadoop 3.0
18 April 2019, eWeek

provided by Google News

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

Share this page