DBMS > Atos Standard Common Repository vs. Google BigQuery vs. Postgres-XL vs. Prometheus vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. Postgres-XL vs. Prometheus vs. SpatiaLite

Editorial information provided by DB-Engines

Name

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

Description

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

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

Open-source Time Series DBMS and monitoring system

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

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

cloud.google.com/bigquery

www.postgres-xl.org

prometheus.io

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

Technical documentation

cloud.google.com/bigquery/docs

www.postgres-xl.org/documentation

prometheus.io/docs

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

Developer

Atos Convergence Creators

Google

Alessandro Furieri

Initial release

2016

2010

2014

since 2012, originally named StormDB

2015

2008

Current release

1703

10 R1, October 2018

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

Apache 2.0

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

hosted

Linux
macOS

Linux
Windows

server-less

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

LDAP

RESTful HTTP/JSON API

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

RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by Federation

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

ACID

MVCC

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

LDAP bind authentication

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

Google Cloud Identity & Access Management (IAM)

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.