DBMS > Atos Standard Common Repository vs. eXtremeDB vs. Google BigQuery vs. Lovefield

System Properties Comparison Atos Standard Common Repository vs. eXtremeDB vs. Google BigQuery vs. Lovefield

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

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

Natively in-memory DBMS with options for persistency, high-availability and clustering

Large scale data warehouse service with append-only tables

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Website

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

www.mcobject.com

cloud.google.com/bigquery

google.github.io/lovefield

Technical documentation

www.mcobject.com/docs/extremedb.htm

cloud.google.com/bigquery/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Atos Convergence Creators

McObject

Google

Initial release

2016

2001

2010

2014

Current release

1703

8.2, 2021

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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 and C++

JavaScript

Server operating systems

Linux

AIX
HP-UX
Linux
macOS
Solaris
Windows

hosted

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

tested with Chrome, Firefox, IE, Safari

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

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

support of XML interfaces available

Secondary indexes

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

LDAP

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

.Net
C
C#
C++
Java
Lua
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

by defining events

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning / sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

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.