DBMS > Atos Standard Common Repository vs. BaseX vs. etcd vs. EXASOL vs. Google BigQuery

System Properties Comparison Atos Standard Common Repository vs. BaseX vs. etcd vs. EXASOL vs. Google BigQuery

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

A distributed reliable key-value store

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

Primary database model

Document store
Key-value store

Native XML DBMS

Key-value store

Relational DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

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

basex.org

etcd.io
github.com/etcd-io/etcd

www.exasol.com

cloud.google.com/bigquery

Technical documentation

docs.basex.org

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

Developer

Atos Convergence Creators

BaseX GmbH

Exasol

Google

Initial release

2016

2007

2000

2010

Current release

1703

10.7, August 2023

3.4, August 2019

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache Version 2.0

commercial

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

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
Windows

experimental

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

XQuery supports types

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

LDAP

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

gRPC
JSON over HTTP

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

via events

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

multiple readers, single writer

ACID

Since BigQuery is designed for querying data

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

Users with fine-grained authorization concept on 4 levels

Access rights for users, groups and roles according to SQL-standard

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.