DBMS > Couchbase vs. Kdb vs. PouchDB vs. RavenDB

System Properties Comparison Couchbase vs. Kdb vs. PouchDB vs. RavenDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

High performance Time Series DBMS

JavaScript DBMS with an API inspired by CouchDB

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store

Time Series DBMS
Vector DBMS

Document store

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

Technical documentation

Developer

Couchbase, Inc.

Kx Systems, a division of First Derivatives plc

Apache Software Foundation

Hibernating Rhinos

Initial release

2011

2000

kdb was released 2000, kdb+ in 2003

2012

2010

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.6, May 2018

7.1.1, June 2019

5.4, July 2022

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

free 32-bit version

Open Source

AGPL version 3, commercial license available

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

C, C++, Go and Erlang

JavaScript

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

table attribute 'grouped'

yes

via views

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (q)

SQL-like query language (RQL)

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

user defined functions

View functions in JavaScript

yes

Triggers

yes

via the TAP protocol

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

similar paradigm used for internal processing

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

rights management via user accounts

Authorization levels configured per client per database

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.