DBMS > Apache Phoenix vs. Atos Standard Common Repository vs. Faircom DB

System Properties Comparison Apache Phoenix vs. Atos Standard Common Repository vs. Faircom DB

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store
Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Website

phoenix.apache.org

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

www.faircom.com/products/faircom-db

Technical documentation

phoenix.apache.org

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

Developer

Apache Software Foundation

Atos Convergence Creators

FairCom Corporation

Initial release

2014

2016

1979

Current release

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

1703

V12, November 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Restricted, free version available

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

ANSI C, C++

Server operating systems

Linux
Unix
Windows

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Data scheme

yes

late-bound, schema-on-read capabilities

Schema and schema-less with LDAP views

schema free, schema optional, schema required, partial schema,

Typing

predefined data types such as float or date

yes

optional

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

yes

yes, ANSI SQL with proprietary extensions

APIs and other access methods

JDBC

LDAP

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Supported programming languages

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

All languages with LDAP bindings

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

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

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

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

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

Amazon EMR 4.7.0 – Apache Tez & Phoenix, Updates to Existing Apps | Amazon Web Services
2 June 2016, AWS Blog

provided by Google News

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

provided by Google News

Share this page