DBMS > Couchbase vs. Firebase Realtime Database vs. KairosDB vs. Microsoft Access vs. NuoDB

System Properties Comparison Couchbase vs. Firebase Realtime Database vs. KairosDB vs. Microsoft Access vs. NuoDB

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Distributed Time Series DBMS based on Cassandra or H2

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.)

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Primary database model

Document store

Time Series DBMS

Relational 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	17.30
Rank	#36	Overall
	#5	Document stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Website

www.couchbase.com

firebase.google.com/products/realtime-database

github.com/kairosdb/kairosdb

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

www.3ds.com/nuodb-distributed-sql-database

Technical documentation

docs.couchbase.com

firebase.google.com/docs/database

kairosdb.github.io

developer.microsoft.com/en-us/access

doc.nuodb.com

Developer

Couchbase, Inc.

Google

acquired by Google 2014

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2011

2012

2013

1992

2013

Current release

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

1.2.2, November 2018

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

limited edition free

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

Java

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

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

yes

but not compliant to any SQL standard

yes

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

Android
iOS
JavaScript API
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java
JavaScript
Objective-C

Java
JavaScript

Node.js
PHP
Python

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

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

Server-side scripts

Stored procedures

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

limited functionality with using 'rules'

yes

since Access 2010 using the ACE-engine

Java, SQL

Triggers

yes

via the TAP protocol

Callbacks are triggered when data changes

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

based on Cassandra

none

data is dynamically stored/cached on the nodes where it is read/written

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

selectable replication factor

based on Cassandra

none

yes

Managed transparently by NuoDB

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

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

but no files for transaction logging

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

Temporary table

User concepts

Access control

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

yes, based on authentication and database rules

simple password-based access control

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

Standard SQL roles/ privileges, Administrative Users

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.