DBMS > BoltDB vs. Couchbase vs. Memcached vs. TerminusDB

System Properties Comparison BoltDB vs. Couchbase vs. Memcached vs. TerminusDB

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

In-memory key-value store, originally intended for caching

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

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

Document store
RDF store

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/boltdb/bolt

www.couchbase.com

www.memcached.org

terminusdb.com

Technical documentation

docs.couchbase.com

github.com/memcached/memcached/wiki

terminusdb.github.io/terminusdb/#

Developer

Couchbase, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

DataChemist Ltd.

Initial release

2013

2011

2003

2018

Current release

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

1.6.27, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

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

Open Source

BSD license

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

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 (WOQL)

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

Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

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

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

Ephemeral buckets

User concepts

Access control

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Role-based access control

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.