DBMS > Atos Standard Common Repository vs. FatDB vs. SAP HANA vs. Tibero vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. FatDB vs. SAP HANA vs. Tibero vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines 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.

In-memory, column based data store. Available as appliance or cloud service

A secure RDBMS, designed for easy portability from Oracle

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

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

www.sap.com/products/hana.html

us.tmaxsoft.com/products/tibero

yaacomo.com

Technical documentation

help.sap.com/hana

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Atos Convergence Creators

FatCloud

SAP

TmaxSoft

Q2WEB GmbH

Initial release

2016

2012

2010

2003

2009

Current release

1703

2.0 SPS07 (April 4, 2023), April 2023

6, April 2015

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and Assembler

Server operating systems

Linux

Windows

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

Android
Linux
Windows

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

APIs and other access methods

LDAP

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

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

via applications

SQLScript, R

Persistent Stored Procedure (PSM)

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

horizontal partitioning

by range, hash, list or composite

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

Multi-source replication
Source-replica replication

Source-replica replication

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

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

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

planned for next version

yes

User concepts

Access control

LDAP bind authentication

Can implement custom security layer via applications

yes

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

fine grained access rights according to SQL-standard

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.