DBMS > Atos Standard Common Repository vs. Bangdb vs. Drizzle vs. SwayDB

System Properties Comparison Atos Standard Common Repository vs. Bangdb vs. Drizzle vs. SwayDB

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.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded 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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

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

bangdb.com

swaydb.simer.au

Technical documentation

docs.bangdb.com

Developer

Atos Convergence Creators

Sachin Sinha, BangDB

Drizzle project, originally started by Brian Aker

Simer Plaha

Initial release

2016

2012

2008

2018

Current release

1703

BangDB 2.0, October 2021

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

BSD 3

Open Source

GNU GPL

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

C++

Scala

Server operating systems

Linux

FreeBSD
Linux
OS X

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: 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

SQL

Support of SQL

SQL like support with command line tool

yes

with proprietary extensions

APIs and other access methods

LDAP

Proprietary protocol
RESTful HTTP API

JDBC

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Java
Python

C
C++
Java
PHP

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

yes

yes, Notifications (with Streaming only)

hooks for callbacks inside the server can be used.

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Multi-source replication
Source-replica replication

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

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

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)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Share this page