DBMS > Atos Standard Common Repository vs. Graphite vs. Oracle Berkeley DB vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Graphite vs. Oracle Berkeley DB vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used in-process key-value store

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

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

github.com/graphite-project/graphite-web

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

yaacomo.com

Technical documentation

graphite.readthedocs.io

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

Developer

Atos Convergence Creators

Chris Davis

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Q2WEB GmbH

Initial release

2016

2006

1994

2009

Current release

1703

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Python

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

Server operating systems

Linux

Linux
Unix

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

Numeric data only

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

yes

APIs and other access methods

LDAP

HTTP API
Sockets

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

JavaScript (Node.js)
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

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

none

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

Concurrency

Support for concurrent manipulation of data

yes

locking

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

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

DB-Engines blog posts

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Grafana Labs Announces Mimir Time Series Database
1 April 2022, Datanami

The Billion Data Point Challenge: Building a Query Engine for High Cardinality Time Series Data
10 December 2018, Uber

Getting Started with Monitoring using Graphite
23 January 2015, InfoQ.com

The value of time series data and TSDBs
10 June 2021, InfoWorld

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google News

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

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

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

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

Motorola A780 Linux based smartphone to have mobile database
14 September 2004, Geekzone

provided by Google News

Share this page