DBMS > Atos Standard Common Repository vs. Bangdb vs. BoltDB vs. Heroic vs. SwayDB

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

Converged and high performance database for device data, events, time series, document and graph

An embedded key-value store for Go.

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

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

Document store
Graph DBMS
Time Series DBMS

Key-value store

Time Series DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Website

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

bangdb.com

github.com/boltdb/bolt

github.com/spotify/heroic

swaydb.simer.au

Technical documentation

docs.bangdb.com

spotify.github.io/heroic

Developer

Atos Convergence Creators

Sachin Sinha, BangDB

Spotify

Simer Plaha

Initial release

2016

2012

2013

2014

2018

Current release

1703

BangDB 2.0, October 2021

License

Commercial or Open Source

commercial

Open Source

BSD 3

Open Source

MIT License

Open Source

Apache 2.0

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

Java

Scala

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

yes: string, long, double, int, geospatial, stream, events

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

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

via Elasticsearch

SQL

Support of SQL

SQL like support with command line tool

APIs and other access methods

LDAP

Proprietary protocol
RESTful HTTP API

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

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Java
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

yes

yes, Notifications (with Streaming only)

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor, Knob for CAP (enterprise version only)

none

yes

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

Tunable consistency, set CAP knob accordingly

none

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

yes

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes

yes, run db with in-memory only mode

yes

User concepts

Access control

LDAP bind authentication

yes (enterprise version only)

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

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

Three Reasons DevOps Should Consider Rocky Linux 9.4
15 May 2024, DevOps.com

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

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

provided by Google News

Share this page