DBMS > Atos Standard Common Repository vs. Datomic vs. Heroic vs. Oracle Berkeley DB

System Properties Comparison Atos Standard Common Repository vs. Datomic vs. Heroic 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.

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Relational DBMS

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.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	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

www.datomic.com

github.com/spotify/heroic

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

Technical documentation

docs.datomic.com

spotify.github.io/heroic

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

Developer

Atos Convergence Creators

Cognitect

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2012

2014

1994

Current release

1703

1.0.6735, June 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

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

Java, Clojure

Java

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

Server operating systems

Linux

All OS with a Java VM

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

LDAP

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

All languages with LDAP bindings

Clojure
Java

.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

Transaction Functions

Triggers

yes

By using transaction functions

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

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

Eventual Consistency
Immediate Consistency

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

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

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Brazil’s Nubank acquires US software firm Cognitect, creator of Clojure and Datomic
24 July 2020, LatamList

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google 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

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

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