DBMS > Apache Druid vs. Microsoft Access vs. MonetDB vs. RocksDB

System Properties Comparison Apache Druid vs. Microsoft Access vs. MonetDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A relational database management system that stores data in columns

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

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

druid.apache.org

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

www.monetdb.org

rocksdb.org

Technical documentation

druid.apache.org/docs/latest/design

developer.microsoft.com/en-us/access

www.monetdb.org/Documentation

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Microsoft

MonetDB BV

Facebook, Inc.

Initial release

2012

1992

2004

2013

Current release

29.0.1, April 2024

1902 (16.0.11328.20222), March 2019

Dec2023 (11.49), December 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Bundled with Microsoft Office

Open Source

Mozilla Public License 2.0

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

Linux
OS X
Unix

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-less columns are supported

yes

schema-free

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 for querying

yes

but not compliant to any SQL standard

yes

SQL 2003 with some extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes, in SQL, C, R

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding via remote tables

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

Source-replica replication available in experimental status

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

fine grained access rights according to SQL-standard

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.