DBMS > BigchainDB vs. Couchbase vs. GeoMesa vs. TimesTen vs. Tkrzw

System Properties Comparison BigchainDB vs. Couchbase vs. GeoMesa vs. TimesTen vs. Tkrzw

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

In-Memory RDBMS compatible to Oracle

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.bigchaindb.com

www.couchbase.com

www.geomesa.org

www.oracle.com/database/technologies/related/timesten.html

dbmx.net/tkrzw

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchbase.com

www.geomesa.org/documentation/stable/user/index.html

docs.oracle.com/database/timesten-18.1

Developer

Couchbase, Inc.

CCRi and others

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Mikio Hirabayashi

Initial release

2016

2011

2014

1998

2020

Current release

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

5.0.0, May 2024

11 Release 2 (11.2.2.8.0)

0.9.3, August 2020

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

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

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

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

Scala

C++

Server operating systems

Linux

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
macOS

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

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
RESTful HTTP API

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C++
Java
PL/SQL

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

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

PL/SQL

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

including cross data center replication
Source-replica replication

depending on storage layer

Multi-source replication
Source-replica replication

none

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

depending on storage layer

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

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

yes

Ephemeral buckets

depending on storage layer

yes

using specific database classes

User concepts

Access control

yes

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

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.