DBMS > Apache Drill vs. Elasticsearch vs. Graph Engine vs. Milvus vs. Redis

System Properties Comparison Apache Drill vs. Elasticsearch vs. Graph Engine vs. Milvus vs. Redis

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A DBMS designed for efficient storage of vector data and vector similarity searches

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Primary database model

Document store
Relational DBMS

Search engine

Graph DBMS
Key-value store

Vector DBMS

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.81
Rank	#144	Overall
	#5	Vector DBMS

Score	156.44
Rank	#6	Overall
	#1	Key-value stores

Website

drill.apache.org

www.elastic.co/elasticsearch

www.graphengine.io

milvus.io

redis.com
redis.io

Technical documentation

drill.apache.org/docs

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

www.graphengine.io/docs/manual

milvus.io/docs/overview.md

docs.redis.com/latest/index.html
redis.io/docs

Developer

Apache Software Foundation

Elastic

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2010

2019

2009

Current release

1.20.3, January 2023

8.6, January 2023

2.3.4, January 2024

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Elastic License

Open Source

MIT License

Open Source

Apache Version 2.0

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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.

Zilliz Cloud – Cloud-native service for Milvus

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

.NET and C

C++, Go

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

.NET

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

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

Vector, Numeric and String

partial

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

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

with RediSearch module

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

with RediSQL module

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C++

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

C#
C++
F#
Visual Basic

C++
Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

yes

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

by using the 'percolation' feature

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

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

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

Depending on the underlying data source

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

Depending on the underlying data source

Memcached and Redis integration

yes

User concepts

Access control

Depending on the underlying data source

Role based access control and fine grained access rights

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

More information provided by the system vendor

Specific characteristics

Milvus is an open-source and cloud-native vector database built for production-ready...
» more

Competitive advantages

Highly available, versatile, and robust with millisecond latency. Supports batch...
» more

Typical application scenarios

RAG: retrieval augmented generation Video media : video understanding, video deduplication....
» more

Key customers

Milvus is trusted by thousands of enterprises, including PayPal, eBay, IKEA, LINE,...
» more

Market metrics

As of January 2024, 25k+ GitHub stars 10M+ downloads and installations 3k+ enterprise...
» more

Licensing and pricing models

Milvus was released under the open-source Apache License 2.0 in October 2019. Fully-managed...
» 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.