DBMS > Atos Standard Common Repository vs. FatDB vs. MySQL vs. TerminusDB

System Properties Comparison Atos Standard Common Repository vs. FatDB vs. MySQL vs. TerminusDB

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Widely used open source RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

www.mysql.com

terminusdb.com

Technical documentation

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

FatCloud

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2016

2012

1995

2018

Current release

1703

8.4.0, April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux

Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

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

Via inetgration in SQL Server

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

LDAP

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

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 journaling

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

Can implement custom security layer via applications

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

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.