DBMS > Hazelcast vs. KeyDB vs. OpenSearch

System Properties Comparison Hazelcast vs. KeyDB vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Key-value store

Search engine

Secondary database models

Document store

JSON support with IMDG 3.12

Vector DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

hazelcast.com

github.com/Snapchat/KeyDB
keydb.dev

github.com/opensearch-project
opensearch.org

Technical documentation

hazelcast.org/imdg/docs

docs.keydb.dev

opensearch.org/docs/latest

Developer

Hazelcast

EQ Alpha Technology Ltd.

Amazon Web Services

Initial release

2008

2019

2021

Current release

5.3.6, November 2023

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD-3

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
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

Java

C++

Java

Server operating systems

All OS with a Java VM

Linux

All OS with a Java VM

Data scheme

schema-free

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

Typing

predefined data types such as float or date

yes

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

by using the Redis Search module

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Lua

yes

Triggers

yes

Events

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication
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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

one or two-phase-commit; repeatable reads; read commited

Optimistic locking, atomic execution of commands blocks and scripts

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

In-memory capabilities

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

yes

User concepts

Access control

Role-based access control

simple password-based access control and ACL

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.