DBMS > BigchainDB vs. Couchbase vs. Geode vs. Kinetica

System Properties Comparison BigchainDB vs. Couchbase vs. Geode vs. Kinetica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Fully vectorized database across both GPUs and CPUs

Primary database model

Document store

Key-value store

Relational DBMS

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

Spatial DBMS
Time Series DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchbase.com

geode.apache.org/docs

docs.kinetica.com

Developer

Couchbase, Inc.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Kinetica

Initial release

2016

2011

2002

2012

Current release

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

1.1, February 2017

7.1, August 2021

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

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

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

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

Python

C, C++, Go and Erlang

Java

C, C++

Server operating systems

Linux

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

yes

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

SQL

Support of SQL

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

SQL-like query language (OQL)

SQL-like DML and DDL statements

APIs and other access methods

CLI Client
RESTful HTTP API

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

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
All JVM based languages
C++
Groovy
Java
Scala

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

user defined functions

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

Source-replica replication

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

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

GPU vRAM or System RAM

User concepts

Access control

yes

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

Access rights per client and object definable

Access rights for users and roles on table 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.