DBMS > CouchDB vs. Hive vs. Riak KV

System Properties Comparison CouchDB vs. Hive vs. Riak KV

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.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Distributed, fault tolerant key-value store

Primary database model

Document store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	17.16
Rank	#41	Overall
	#7	Document stores

Score	81.58
Rank	#17	Overall
	#11	Relational DBMS

Score	6.52
Rank	#65	Overall
	#9	Key-value stores

Website

couchdb.apache.org

hive.apache.org

riak.com/products/riak-kv

Technical documentation

docs.couchdb.org/en/stable

cwiki.apache.org/confluence/display/Hive/Home

Developer

Apache Software Foundation

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

Apache Software Foundation

initially developed by Facebook

Basho Technologies

Initial release

2005

2012

2009

Current release

3.2.2, April 2022

3.1.2, August 2019

2.1.0, April 2015

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache Version 2

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
OS X

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.

Secondary indexes

yes

via views

yes

restricted

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

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

C++
Java
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

View functions in JavaScript

yes

user defined functions and integration of map-reduce

JavaScript and Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

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.

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles

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.