DBMS > Apache Phoenix vs. Atos Standard Common Repository vs. MySQL vs. PouchDB vs. SpaceTime

System Properties Comparison Apache Phoenix vs. Atos Standard Common Repository vs. MySQL vs. PouchDB vs. SpaceTime

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

Widely used open source RDBMS

JavaScript DBMS with an API inspired by CouchDB

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.93
Rank	#120	Overall
	#59	Relational DBMS

Score	1017.80
Rank	#2	Overall
	#2	Relational DBMS

Score	2.08
Rank	#116	Overall
	#21	Document stores

Score	0.00
Rank	#386	Overall
	#7	Spatial DBMS

Website

phoenix.apache.org

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

www.mysql.com

pouchdb.com

www.mireo.com/spacetime

Technical documentation

phoenix.apache.org

dev.mysql.com/doc

pouchdb.com/guides

Developer

Apache Software Foundation

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Mireo

Initial release

2014

2016

1995

2012

2020

Current release

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

1703

9.0.0, July 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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

C and C++

JavaScript

C++

Server operating systems

Linux
Unix
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

Schema and schema-less with LDAP views

yes

schema-free

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

Secondary indexes

yes

via views

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP API

Supported programming languages

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

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users with fine-grained authorization concept

no user groups or roles

yes

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.