DBMS > Apache Druid vs. Elasticsearch vs. EventStoreDB vs. Microsoft Access vs. RocksDB

System Properties Comparison Apache Druid vs. Elasticsearch vs. EventStoreDB vs. Microsoft Access vs. RocksDB

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

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

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector 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	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Website

druid.apache.org

www.elastic.co/elasticsearch

www.eventstore.com

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

rocksdb.org

Technical documentation

druid.apache.org/docs/latest/design

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

developers.eventstore.com

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Elastic

Event Store Limited

Microsoft

Facebook, Inc.

Initial release

2012

2010

2012

1992

2013

Current release

29.0.1, April 2024

8.6, January 2023

21.2, February 2021

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Elastic License

Open Source

commercial

Bundled with Microsoft Office

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

All OS with a Java VM

Linux
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

by using the 'percolation' feature

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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.

Memcached and Redis integration

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

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.