DBMS > etcd vs. KeyDB vs. Microsoft Access vs. OpenSearch

System Properties Comparison etcd vs. KeyDB vs. Microsoft Access vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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 distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Key-value store

Relational DBMS

Search engine

Secondary database models

Vector DBMS

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

etcd.io
github.com/etcd-io/etcd

github.com/Snapchat/KeyDB
keydb.dev

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

github.com/opensearch-project
opensearch.org

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.keydb.dev

developer.microsoft.com/en-us/access

opensearch.org/docs/latest

Developer

EQ Alpha Technology Ltd.

Microsoft

Amazon Web Services

Initial release

2019

1992

2021

Current release

3.4, August 2019

1902 (16.0.11328.20222), March 2019

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD-3

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++

Java

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

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

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

gRPC
JSON over HTTP

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
DAO
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

Lua

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes, watching key changes

yes

since Access 2010 using the ACE-engine

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.