DBMS > Atos Standard Common Repository vs. gStore vs. OrigoDB

System Properties Comparison Atos Standard Common Repository vs. gStore vs. OrigoDB

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

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

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Document store
Object oriented 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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

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

en.gstore.cn

origodb.com

Technical documentation

en.gstore.cn/#/enDocs

origodb.com/docs

Developer

Atos Convergence Creators

Robert Friberg et al

Initial release

2016

2009

under the name LiveDB

Current release

1703

1.2, November 2023

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

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

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free and OWL/RDFS-schema support

yes

Typing

predefined data types such as float or date

optional

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

LDAP

HTTP API
SPARQL 1.1

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages with LDAP bindings

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

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica 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

Foreign keys

Referential integrity

depending on model

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

Durability

Support for making data persistent

yes

Write ahead log

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

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

Role based authorization

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.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Share this page