DBMS > Atos Standard Common Repository vs. IRONdb vs. Oracle Berkeley DB

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

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.

IRONdb 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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used in-process key-value store

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

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

Score	1.71
Rank	#129	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

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

www.circonus.com/solutions/time-series-database/

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

Technical documentation

docs.circonus.com/irondb/category/getting-started

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

Developer

Atos Convergence Creators

Circonus LLC.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2017

1994

Current release

1703

V0.10.20, January 2018

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

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)

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

LDAP

HTTP API

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.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

yes, in Lua

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

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 per node, eventual consistency across nodes

Foreign keys

Referential integrity

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

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

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

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

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
5 March 2019, ADTmag

Which Are the Top Local Databases for React Native
15 October 2019, appinventiv.com

Fig. 2. XML Methods for Various XML DBMS Types
29 October 2024, ResearchGate

Introduction to Sybase, Part 2
1 July 1999, Linux Journal

provided by Google News

Share this page