DBMS > Atos Standard Common Repository vs. etcd vs. eXtremeDB vs. MySQL vs. Tarantool

System Properties Comparison Atos Standard Common Repository vs. etcd vs. eXtremeDB vs. MySQL vs. Tarantool

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

A distributed reliable key-value store

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

Widely used open source RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	0.73
Rank	#227	Overall
	#104	Relational DBMS
	#18	Time Series DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

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

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

www.mcobject.com

www.mysql.com

www.tarantool.io

Technical documentation

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

www.mcobject.com/docs/extremedb.htm

dev.mysql.com/doc

www.tarantool.io/en/doc

Developer

Atos Convergence Creators

McObject

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2001

1995

2008

Current release

1703

3.4, August 2019

8.2, 2021

8.3.0, January 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

AIX
HP-UX
Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

optional

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

LDAP

gRPC
JSON over HTTP

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

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

Supported programming languages

All languages with LDAP bindings

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

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

yes

yes, watching key changes

yes

by defining events

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning / sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

yes

table locks or row locks depending on storage engine

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

LDAP bind authentication

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» more

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.