DBMS > Couchbase vs. Derby vs. GeoMesa vs. Microsoft Access

System Properties Comparison Couchbase vs. Derby vs. GeoMesa vs. Microsoft Access

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

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	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

www.couchbase.com

db.apache.org/derby

www.geomesa.org

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

Technical documentation

docs.couchbase.com

db.apache.org/derby/manuals/index.html

www.geomesa.org/documentation/stable/user/index.html

developer.microsoft.com/en-us/access

Developer

Couchbase, Inc.

Apache Software Foundation

CCRi and others

Microsoft

Initial release

2011

1997

2014

1992

Current release

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

10.17.1.0, November 2023

4.0.5, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

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

Open Source

Apache version 2

Open Source

Apache License 2.0

commercial

Bundled with Microsoft Office

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

Java

Scala

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

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.

yes

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

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

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

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

Server-side scripts

Stored procedures

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

Java Stored Procedures

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

Automatic Sharding

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

depending on storage layer

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

Immediate Consistency

depending on storage layer

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

but no files for transaction logging

In-memory capabilities

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

yes

Ephemeral buckets

yes

depending on storage layer

User concepts

Access control

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.