DBMS > CouchDB vs. IRONdb vs. Snowflake vs. Tkrzw

System Properties Comparison CouchDB vs. IRONdb vs. Snowflake vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

Cloud-based data warehousing service for structured and semi-structured data

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

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	123.20
Rank	#9	Overall
	#6	Relational DBMS

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

Website

couchdb.apache.org

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

www.snowflake.com

dbmx.net/tkrzw

Technical documentation

docs.couchdb.org/en/stable

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

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

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

Circonus LLC.

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2005

2017

2014

2020

Current release

3.3.3, December 2023

V0.10.20, January 2018

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

C and C++

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux

hosted

Linux
macOS

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

via views

SQL

Support of SQL

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

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes, in Lua

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic, metric affinity per node

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

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

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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.