DBMS > Atos Standard Common Repository vs. Heroic vs. SQLite vs. SwayDB vs. TerminusDB

System Properties Comparison Atos Standard Common Repository vs. Heroic vs. SQLite vs. SwayDB vs. TerminusDB

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used embeddable, in-process RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

Primary database model

Document store
Key-value store

Secondary database models

Document store
RDF store

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

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

github.com/spotify/heroic

www.sqlite.org

swaydb.simer.au

terminusdb.com

Technical documentation

spotify.github.io/heroic

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

Spotify

Dwayne Richard Hipp

Simer Plaha

DataChemist Ltd.

Initial release

2016

2014

2000

2018

Current release

1703

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

GNU Affero GPL V3.0

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

Scala

Prolog, Rust

Server operating systems

Linux

server-less

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

dynamic column types

schema-free

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

LDAP

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Java
Kotlin
Scala

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

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

Atomic execution of 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

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.