DBMS > Atos Standard Common Repository vs. gStore vs. Oracle Berkeley DB vs. VelocityDB

System Properties Comparison Atos Standard Common Repository vs. gStore vs. Oracle Berkeley DB vs. VelocityDB

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.

Widely used in-process key-value store

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS
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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

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

en.gstore.cn

www.oracle.com/database/technologies/related/berkeleydb.html

velocitydb.com

Technical documentation

en.gstore.cn/#/enDocs

docs.oracle.com/cd/E17076_05/html/index.html

velocitydb.com/UserGuide

Developer

Atos Convergence Creators

Oracle

originally developed by Sleepycat, which was acquired by Oracle

VelocityDB Inc

Initial release

2016

1994

2011

Current release

1703

1.2, November 2023

18.1.40, May 2020

7.x

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

commercial license available

commercial

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++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Any that supports .NET

Data scheme

Schema and schema-less with LDAP views

schema-free and OWL/RDFS-schema support

schema-free

yes

Typing

predefined data types such as float or date

optional

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

LDAP

HTTP API
SPARQL 1.1

.Net

Supported programming languages

All languages with LDAP bindings

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

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

Immediate Consistency

Foreign keys

Referential integrity

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

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

Based on Windows Authentication

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

How to store financial market data for backtesting
26 January 2019, Towards Data Science

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Share this page