DBMS > Derby vs. Microsoft Access vs. RethinkDB vs. RocksDB

System Properties Comparison Derby vs. Microsoft Access vs. RethinkDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Spatial DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

db.apache.org/derby

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

rethinkdb.com

rocksdb.org

Technical documentation

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

developer.microsoft.com/en-us/access

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Microsoft

The Linux Foundation

since July 2017

Facebook, Inc.

Initial release

1997

1992

2009

2013

Current release

10.17.1.0, November 2023

1902 (16.0.11328.20222), March 2019

2.4.1, August 2020

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2

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

Java

C++

Server operating systems

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

Java

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

range based

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

Atomic single-document operations

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

yes

users and table-level permissions

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.