DBMS > Atos Standard Common Repository vs. Linter vs. Oracle Berkeley DB vs. TinkerGraph

System Properties Comparison Atos Standard Common Repository vs. Linter vs. Oracle Berkeley DB vs. TinkerGraph

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

RDBMS for high security requirements

Widely used in-process key-value store

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

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

linter.ru

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

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

Developer

Atos Convergence Creators

relex.ru

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

1990

1994

2009

Current release

1703

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache 2.0

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

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

Java

Server operating systems

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

TinkerPop 3

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.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

Groovy
Java

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Durability

Support for making data persistent

yes

optional

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

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

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, HPCwire

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

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

provided by Google News

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune | Amazon Web Services
3 June 2024, AWS Blog

Simple Deployment of a Graph Database: JanusGraph | by Edward Elson Kosasih
12 October 2020, Towards Data Science

Why developers like Apache TinkerPop, an open source framework for graph computing | Amazon Web Services
27 September 2021, AWS Blog

InfiniteGraph Gets Support for Common Graph Database Language and More
21 February 2012, SiliconANGLE News

Introducing Gremlin query hints for Amazon Neptune | AWS Database Blog
26 February 2019, AWS Blog

provided by Google News

Share this page