DBMS > BoltDB vs. Couchbase vs. Google Cloud Datastore vs. RocksDB vs. Tigris

System Properties Comparison BoltDB vs. Couchbase vs. Google Cloud Datastore vs. RocksDB vs. Tigris

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Key-value store

Document store

Key-value store

Document store
Key-value store
Search engine
Time Series 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

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

github.com/boltdb/bolt

www.couchbase.com

cloud.google.com/datastore

rocksdb.org

www.tigrisdata.com

Technical documentation

docs.couchbase.com

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

www.tigrisdata.com/docs

Developer

Couchbase, Inc.

Google

Facebook, Inc.

Tigris Data, Inc.

Initial release

2013

2011

2008

2013

2022

Current release

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

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

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

commercial

Open Source

BSD

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

Linux

Linux
macOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

C++ API
Java API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

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

using Google App Engine

Triggers

yes

via the TAP protocol

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users 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.