DBMS > Atos Standard Common Repository vs. CockroachDB vs. Heroic vs. SQLite vs. SwayDB

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Widely used embeddable, in-process RDBMS

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

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

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

Website

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

www.cockroachlabs.com

github.com/spotify/heroic

www.sqlite.org

swaydb.simer.au

Technical documentation

www.cockroachlabs.com/docs

spotify.github.io/heroic

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Cockroach Labs

Spotify

Dwayne Richard Hipp

Simer Plaha

Initial release

2016

2015

2014

2000

2018

Current release

1703

24.1.0, May 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

Apache 2.0

Open Source

Public Domain

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

Scala

Server operating systems

Linux

Linux
macOS
Windows

server-less

Data scheme

Schema and schema-less with LDAP views

dynamic schema

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

via Elasticsearch

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

JDBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

via file-system locks

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

Role-based access control

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.