Databases 14 min read

RedisJSON vs MongoDB & ElasticSearch: Why It Outperforms by Up to 500×

Benchmark tests reveal that RedisJSON, powered by RediSearch, dramatically outperforms MongoDB and ElasticSearch across isolated reads and writes, mixed workloads, and latency metrics, delivering up to 500‑fold speed gains, lower latency, and higher throughput, making it a compelling choice for modern data‑intensive applications.

Programmer DD
Programmer DD
Programmer DD
RedisJSON vs MongoDB & ElasticSearch: Why It Outperforms by Up to 500×

Recent official reports show that RedisJSON (with RediSearch) delivers performance that far exceeds other NoSQL solutions.

Isolated writes: RedisJSON is 5.4× faster than MongoDB and more than 200× faster than ElasticSearch.

Isolated reads: RedisJSON is 12.7× faster than MongoDB and over 500× faster than ElasticSearch.

In mixed‑workload scenarios, real‑time updates do not degrade RedisJSON’s search or read performance, whereas ElasticSearch suffers noticeable slowdowns.

RedisJSON supports roughly 50× more operations per second than MongoDB and 7× more than ElasticSearch.

Latency is about 90× lower than MongoDB and 23.7× lower than ElasticSearch at higher percentiles.

Query Engine

The development of reresearch and RedisJSON places strong emphasis on performance, providing analysis tools and detectors for developers.

Loading Optimization

NYC taxi benchmark results demonstrate substantial performance improvements with each new reresearch version.

Each new version shows a tangible performance gain.

Full‑text Search Optimization

Indexing 5.9 million Wikipedia abstracts and running full‑text search queries produced significant improvements in write, read, and search latency when moving from v2.0 to v2.2.

Comparison with Other Frameworks

RedisJSON is compared against MongoDB and ElasticSearch in terms of document storage, availability, professional support, scalability, and overall performance.

Benchmark Setup

Software environment used:

MongoDB v5.0.3

ElasticSearch 7.15

RedisJSON (RediSearch 2.2 + RedisJSON 2.0)

Benchmarks were run on AWS m5d.8xlarge instances with four VMs (one client, three database servers) in a single availability zone to ensure low latency and stable network performance.

100% Write Benchmark

RedisJSON ingestion speed is 8.8× faster than ElasticSearch and 1.8× faster than MongoDB, maintaining sub‑millisecond latency. It is the only solution that updates its index on every write, avoiding the near‑real‑time (NRT) delay seen in ElasticSearch.

100% Read Benchmark

RedisJSON reads are 15.8× faster than ElasticSearch and 2.8× faster than MongoDB, with latency staying in the sub‑millisecond range.

Mixed Read/Write/Search Benchmark

A realistic mix of 65 % search and 35 % read (plus 10 % writes) shows that RedisJSON maintains throughput while ElasticSearch’s performance degrades as write proportion increases.

Full Latency Analysis

Across all latency percentiles, RedisJSON consistently stays in the sub‑millisecond range, outperforming MongoDB and ElasticSearch. For example, RedisJSON’s p99 latency is 0.23 ms versus 5.01 ms for MongoDB and 10.49 ms for ElasticSearch.

How to Get Started

You can create a free Redis cloud database in any region or run RedisJSON via a Docker container. Documentation has been updated to help developers quickly start using query and search features.

Node.js – node-redis

Java – Jedis

.NET – NRedisJSON, NRediSearch

Python – redis-py

Reference: RedisJSON Public Preview & Performance Benchmarking.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

search engineperformance benchmarkdatabase comparisonNoSQLYCSBRedisJSON
Programmer DD
Written by

Programmer DD

A tinkering programmer and author of "Spring Cloud Microservices in Action"

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.