DBMS > Atos Standard Common Repository vs. STSdb vs. ToroDB vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. STSdb vs. ToroDB vs. Yanza

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.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Key-value store

Document store

Time Series DBMS

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

github.com/STSSoft/STSdb4

github.com/torodb/server

yanza.com

Developer

Atos Convergence Creators

STS Soft SC

8Kdata

Yanza

Initial release

2016

2011

2016

2015

Current release

1703

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux

Windows

All OS with a Java 7 VM

Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

primitive types and user defined types (classes)

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

LDAP

.NET Client API

HTTP API

Supported programming languages

All languages with LDAP bindings

C#
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

none

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

Transaction concepts

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

Atomic execution of specific operations

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

User concepts

Access control

LDAP bind authentication

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page