DBMS > Atos Standard Common Repository vs. MySQL vs. OpenMLDB vs. SpaceTime

System Properties Comparison Atos Standard Common Repository vs. MySQL vs. OpenMLDB vs. SpaceTime

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

Widely used open source RDBMS

An open-source machine learning database that provides a feature platform for training and inference

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.02
Rank	#367	Overall
	#37	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

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

www.mysql.com

openmldb.ai

www.mireo.com/spacetime

Technical documentation

dev.mysql.com/doc

openmldb.ai/docs/zh/main

Developer

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

4 Paradigm Inc.

Mireo

Initial release

2016

1995

2020

Current release

1703

8.3.0, January 2024

2024-2 February 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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

C++, Java, Scala

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

A subset of ANSI SQL is implemented

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
SQLAlchemy

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

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

C++
Go
Java
Python
Scala

C#
C++
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

Real-time block device replication (DRBD)

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

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

no user groups or roles

fine grained access rights according to SQL-standard

yes

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.