DBMS > Atos Standard Common Repository vs. SQLite vs. TerminusDB vs. YDB

System Properties Comparison Atos Standard Common Repository vs. SQLite vs. TerminusDB vs. YDB

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

Widely used embeddable, in-process RDBMS

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

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Document store
Relational DBMS

Secondary database models

Document store
RDF store

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

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

www.sqlite.org

terminusdb.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

ydb.tech/en/docs

Developer

Atos Convergence Creators

Dwayne Richard Hipp

DataChemist Ltd.

Yandex

Initial release

2016

2000

2018

2019

Current release

1703

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

GPL V3

Open Source

Apache 2.0; commercial license available

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

Prolog, Rust

Server operating systems

Linux

server-less

Linux

Data scheme

Schema and schema-less with LDAP views

yes

dynamic column types

yes

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

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

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

SQL-like query language (YQL)

APIs and other access methods

LDAP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

All languages with LDAP bindings

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

JavaScript
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Journaling Streams

Active-passive shard replication

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

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

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based access control

Access rights defined for Yandex Cloud users

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.