DBMS > Couchbase vs. Dolt vs. FatDB vs. jBASE

System Properties Comparison Couchbase vs. Dolt vs. FatDB vs. jBASE

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A MySQL compatible DBMS with Git-like versioning of data and schema

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A robust multi-value DBMS comprising development tools and middleware

Primary database model

Document store

Relational DBMS

Document store
Key-value store

Multivalue 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

Document store

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Website

www.couchbase.com

github.com/dolthub/dolt
www.dolthub.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

docs.couchbase.com

docs.dolthub.com

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

Couchbase, Inc.

DoltHub Inc

FatCloud

Rocket Software (formerly Zumasys)

Initial release

2011

2018

2012

1991

Current release

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

5.7

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2.0

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

C, C++, Go and Erlang

Server operating systems

Linux
OS X
Windows

Linux
macOS
Windows

Windows

AIX
Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

Via inetgration in SQL Server

Embedded SQL for jBASE in BASIC

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

CLI Client
HTTP REST

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

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

yes

currently in alpha release

yes

via applications

yes

Triggers

yes

via the TAP protocol

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

selectable replication factor

yes

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

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

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.

Only one user is configurable, and must be specified in the config file at startup

Can implement custom security layer via applications

Access rights can be defined down to the item 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.