DBMS > Atos Standard Common Repository vs. CouchDB vs. IRONdb vs. Tkrzw

System Properties Comparison Atos Standard Common Repository vs. CouchDB vs. IRONdb vs. Tkrzw

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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Key-value store

Document store

Time Series DBMS

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

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

couchdb.apache.org

www.circonus.com/solutions/time-series-database/

dbmx.net/tkrzw

Technical documentation

docs.couchdb.org/en/stable

docs.circonus.com/irondb/category/getting-started

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Circonus LLC.

Mikio Hirabayashi

Initial release

2016

2005

2017

2020

Current release

1703

3.3.3, December 2023

V0.10.20, January 2018

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Open Source

Apache Version 2.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

Erlang

C and C++

C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

yes

text, numeric, histograms

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 views

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

LDAP

RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages with LDAP bindings

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

improved architecture with release 2.0

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

none

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

atomic operations within a single document possible

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

using specific database classes

User concepts

Access control

LDAP bind authentication

Access rights for users can be defined per database

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

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Recent citations in the news

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

How to Connect Your Flask App With CouchDB: A NoSQL Database - MUO
14 August 2021, MakeUseOf

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Share this page