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

System Properties Comparison Atos Standard Common Repository vs. Heroic vs. Oracle Berkeley DB vs. SpaceTime vs. SwayDB

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

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

Widely used in-process key-value store

SpaceTime is a spatio-temporal DBMS with a focus on performance.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

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

github.com/spotify/heroic

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

www.mireo.com/spacetime

swaydb.simer.au

Technical documentation

spotify.github.io/heroic

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

Developer

Atos Convergence Creators

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Mireo

Simer Plaha

Initial release

2016

2014

1994

2020

2018

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

Open Source

GNU Affero GPL V3.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, Java, C++ (depending on the Berkeley DB edition)

C++

Scala

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

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

A subset of ANSI SQL is implemented

APIs and other access methods

LDAP

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

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

.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

C#
C++
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Real-time block device replication (DRBD)

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

Eventual Consistency
Immediate 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

Atomic execution of operations

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

yes

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

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

provided by Google News

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

What You Need to Know About NoSQL Databases
17 February 2012, Forbes

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

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

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

provided by Google News

Share this page