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

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

Description

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

Widely used embeddable, in-process RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

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

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

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

www.sqlite.org

www.teradata.com

terminusdb.com

Technical documentation

www.sqlite.org/docs.html

docs.teradata.com

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

Dwayne Richard Hipp

Teradata

DataChemist Ltd.

Initial release

2016

2000

1984

2018

Current release

1703

3.46.1 (13 August 2024), August 2024

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

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.

Implementation language

Java

Prolog, Rust

Server operating systems

Linux

server-less

hosted
Linux

Linux

Data scheme

Schema and schema-less with LDAP views

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

LDAP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Journaling Streams

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

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

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.