DBMS > BigchainDB vs. Couchbase vs. Microsoft Access vs. NSDb

System Properties Comparison BigchainDB vs. Couchbase vs. Microsoft Access vs. NSDb

Please select another system to include it in the comparison.

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Document store

Relational DBMS

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.76
Rank	#216	Overall
	#36	Document stores

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Website

www.bigchaindb.com

www.couchbase.com

www.microsoft.com/en-us/microsoft-365/access

nsdb.io

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchbase.com

developer.microsoft.com/en-us/access

nsdb.io/Architecture

Developer

Couchbase, Inc.

Microsoft

Initial release

2016

2011

1992

2017

Current release

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

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

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

commercial

Bundled with Microsoft Office

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

C++

Java, Scala

Server operating systems

Linux

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

SQL-like query language

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

ADO.NET
DAO
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Java
Scala

Server-side scripts

Stored procedures

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

yes

since Access 2010 using the ACE-engine

Triggers

yes

via the TAP protocol

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

including cross data center 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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

but no files for transaction logging

Using Apache Lucene

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

yes

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

a simple user-level security was built in till version Access 2003

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.