DBMS > Atos Standard Common Repository vs. BigchainDB vs. Cassandra vs. KeyDB

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Cassandra vs. KeyDB

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Document store
Key-value store

Document store

Wide column store

Key-value store

Secondary database models

Vector DBMS

starting with release V5

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Website

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

www.bigchaindb.com

cassandra.apache.org

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

bigchaindb.readthedocs.io/en/latest

cassandra.apache.org/doc/latest

docs.keydb.dev

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top level project, originally developped by Facebook

EQ Alpha Technology Ltd.

Initial release

2016

2008

2019

Current release

1703

4.1.3, July 2023

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache version 2

Open Source

BSD-3

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

Python

Java

C++

Server operating systems

Linux

BSD
Linux
OS X
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

restricted

only equality queries, not always the best performing solution

yes

by using the Redis Search module

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

Atomicity and isolation are supported for single operations

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights for users can be defined per object

simple password-based access control and ACL

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.