DBMS > BoltDB vs. CouchDB vs. EJDB vs. OpenQM vs. Yanza

System Properties Comparison BoltDB vs. CouchDB vs. EJDB vs. OpenQM vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza 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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

QpenQM is a high-performance, self-tuning, multi-value DBMS

Time Series DBMS for IoT Applications

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	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

github.com/boltdb/bolt

couchdb.apache.org

github.com/Softmotions/ejdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

yanza.com

Technical documentation

docs.couchdb.org/en/stable

github.com/Softmotions/ejdb/blob/master/README.md

Developer

Apache Software Foundation

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

Softmotions

Rocket Software, originally Martin Phillips

Yanza

Initial release

2013

2005

2012

1993

2015

Current release

3.3.3, December 2023

3.4-12

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

GPLv2

Open Source

GPLv2, extended commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

server-less

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Windows

Data scheme

schema-free

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

in-process shared library

HTTP API

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

yes

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Read/Write 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.

User concepts

Access control

Access rights for users can be defined per database

Access rights can be defined down to the item level

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

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Three Reasons DevOps Should Consider Rocky Linux 9.4
15 May 2024, DevOps.com

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

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

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

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

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

Tracking Expenses with CouchDB and Angular — SitePoint
28 August 2014, SitePoint

provided by Google News

Share this page