DBMS > Atos Standard Common Repository vs. ITTIA vs. MySQL vs. searchxml

System Properties Comparison Atos Standard Common Repository vs. ITTIA vs. MySQL vs. searchxml

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

Edge Time Series DBMS with Real-Time Stream Processing

Widely used open source RDBMS

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.36
Rank	#272	Overall
	#22	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

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

www.ittia.com

www.mysql.com

www.searchxml.net/category/products

Technical documentation

dev.mysql.com/doc

www.searchxml.net/support/handouts

Developer

Atos Convergence Creators

ITTIA L.L.C.

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Initial release

2016

2007

1995

2015

Current release

1703

8.7

9.0.0, July 2024

1.0

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Implementation language

Java

C and C++

C++

Server operating systems

Linux

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

optional

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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

APIs and other access methods

LDAP

JDBC
ODBC
RESTful HTTP API
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages with LDAP bindings

C
C++
JavaScript (Node.js)
Python

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

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

yes

ACID

not for MyISAM storage engine

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Database file passwords

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.