DBMS > Couchbase vs. GridDB vs. LeanXcale vs. RocksDB

System Properties Comparison Couchbase vs. GridDB vs. LeanXcale vs. RocksDB

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

Scalable in-memory time series database optimized for IoT and Big Data

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

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

Primary database model

Document store

Time Series DBMS

Key-value store
Relational DBMS

Key-value store

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

Key-value store
Relational DBMS

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

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.28
Rank	#286	Overall
	#41	Key-value stores
	#130	Relational DBMS

Score	2.84
Rank	#97	Overall
	#16	Key-value stores

Website

Technical documentation

docs.couchbase.com

docs.griddb.net

github.com/facebook/rocksdb/wiki

Developer

Couchbase, Inc.

Toshiba Corporation

LeanXcale

Facebook, Inc.

Initial release

2011

2013

2015

2013

Current release

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

5.1, August 2022

9.4.0, June 2024

License

Commercial or Open Source

Open Source

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

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

BSD

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

C++

Server operating systems

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

yes

through Apache Derby

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

C++ API
Java API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

ACID

yes

Concurrency

Support for concurrent manipulation of data

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.

Access rights for users can be defined per database

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.