DBMS > Atos Standard Common Repository vs. FatDB vs. gStore vs. SQLite vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. FatDB vs. gStore vs. SQLite 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.

A native Graph DBMS to store and maintain very large RDF datasets.

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

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

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

en.gstore.cn

www.sqlite.org

yaacomo.com

Technical documentation

en.gstore.cn/#/enDocs

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

FatCloud

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2016

2012

2016

2000

2009

Current release

1703

1.2, November 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Public Domain

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

Server operating systems

Linux

Windows

Linux

server-less

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

schema-free and OWL/RDFS-schema support

yes

dynamic column types

yes

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

APIs and other access methods

LDAP

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

HTTP API
SPARQL 1.1

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C++
Java
JavaScript (Node.js)
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Can implement custom security layer via applications

Users, roles and permissions, Role-Based Access Control (RBAC) supported

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.