DBMS > Atos Standard Common Repository vs. Faircom DB vs. Teradata Aster vs. ToroDB

System Properties Comparison Atos Standard Common Repository vs. Faircom DB vs. Teradata Aster vs. ToroDB

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.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Platform for big data analytics on multistructured data sources and types

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Key-value store

Key-value store
Relational DBMS

Relational DBMS

Document store

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

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Website

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

www.faircom.com/products/faircom-db

github.com/torodb/server

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

Developer

Atos Convergence Creators

FairCom Corporation

Teradata

8Kdata

Initial release

2016

1979

2005

2016

Current release

1703

V13, July 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

AGPL-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.

Implementation language

Java

ANSI C, C++

Java

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux

All OS with a Java 7 VM

Data scheme

Schema and schema-less with LDAP views

schema free, schema optional, schema required, partial schema,

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

schema-free

Typing

predefined data types such as float or date

optional

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, integer, double, boolean, date, object_id

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

LDAP

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

fine grained access rights according to SQL-standard

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Teradata's Aster shows how the flowers of fraud bloom
23 April 2015, The Register

Teradata Integrates Big Data Analytic Architecture
22 October 2012, PR Newswire

An American Dream Story, With A Silicon Valley Twist
14 August 2013, Forbes

Gartner, IBM, Teradata make Big Data announcements
17 October 2012, ZDNet

Big Data Use Case – What Is Teradata IntelliCloud?
24 May 2017, insideBIGDATA

provided by Google News

Share this page