DBMS > Apache Phoenix vs. Atos Standard Common Repository vs. Google BigQuery vs. SpatiaLite

System Properties Comparison Apache Phoenix vs. Atos Standard Common Repository vs. Google BigQuery vs. SpatiaLite

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

Large scale data warehouse service with append-only tables

Spatial extension of SQLite

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

phoenix.apache.org

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

cloud.google.com/bigquery

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

Atos Convergence Creators

Google

Alessandro Furieri

Initial release

2014

2016

2010

2008

Current release

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

1703

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Server operating systems

Linux
Unix
Windows

Linux

hosted

server-less

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

LDAP

RESTful HTTP/JSON API

Supported programming languages

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

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

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

Since BigQuery is designed for querying data

ACID

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

LDAP bind authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.