DBMS > Couchbase vs. H2GIS vs. Ingres vs. Riak KV

System Properties Comparison Couchbase vs. H2GIS vs. Ingres vs. Riak KV

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

Spatial extension of H2

Well established RDBMS

Distributed, fault tolerant key-value store

Primary database model

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

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

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.couchbase.com

www.h2gis.org

www.actian.com/databases/ingres

Technical documentation

docs.couchbase.com

www.h2gis.org/docs/home

docs.actian.com/ingres

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Couchbase, Inc.

CNRS

Actian Corporation

OpenSource, formerly Basho Technologies

Initial release

2011

2013

1974

originally developed at University Berkely in early 1970s

2009

Current release

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

11.2, May 2022

3.2.0, December 2022

License

Commercial or Open Source

Open Source

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

Open Source

LGPL 3.0

commercial

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

C, C++, Go and Erlang

Java

Erlang

Server operating systems

Linux
OS X
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

restricted

SQL

Support of SQL

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

yes

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

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

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

yes

based on H2

yes

Erlang

Triggers

yes

via the TAP protocol

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

based on H2

Ingres Replicator

selectable replication factor

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

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

MVCC

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

Ephemeral buckets

yes

User concepts

Access control

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

yes

based on H2

fine grained access rights according to SQL-standard

yes, using Riak Security

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.