DBMS > CouchDB vs. Datomic vs. RocksDB vs. SiteWhere

System Properties Comparison CouchDB vs. Datomic vs. RocksDB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

M2M integration platform for persisting/querying time series data

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	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

couchdb.apache.org

www.datomic.com

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

docs.couchdb.org/en/stable

docs.datomic.com

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

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

Cognitect

Facebook, Inc.

SiteWhere

Initial release

2005

2012

2013

2010

Current release

3.3.3, December 2023

1.0.7075, December 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

limited edition free

Open Source

BSD

Open Source

Common Public Attribution License Version 1.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

Erlang

Java, Clojure

C++

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

C++ API
Java API

HTTP REST

Supported programming languages

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

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Transaction Functions

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

But extensive use of caching in the application peers

yes

selectable replication factor

based on HBase

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

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per database

Users with fine-grained authorization concept

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.