StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Search
  4. Search As A Service
  5. Elasticsearch vs Redis

Elasticsearch vs Redis

OverviewDecisionsComparisonAlternatives

Overview

Elasticsearch
Elasticsearch
Stacks35.5K
Followers27.1K
Votes1.6K
Redis
Redis
Stacks61.9K
Followers46.5K
Votes3.9K
GitHub Stars42
Forks6

Elasticsearch vs Redis: What are the differences?

Elasticsearch and Redis are both popular open-source databases, but they have key differences in terms of functionality and use cases.

  1. Search vs Caching: Elasticsearch is primarily a search engine that is designed for indexing and querying large amounts of data. It is optimized for fast search and retrieval of structured and unstructured data. On the other hand, Redis is an in-memory data structure store that is often used for caching data. It excels at storing and retrieving small pieces of data quickly.

  2. Data Model: Elasticsearch uses a document-oriented data model, where data is stored in JSON documents. These documents can be organized into indices and are indexed and searchable using various fields and attributes. Redis, on the other hand, is a key-value store that stores and retrieves data using a simple key and value structure.

  3. Data Persistence: Elasticsearch is designed for durability and data persistence. It provides mechanisms for creating replicas of data and automatic sharding for distributed storage. Redis, on the other hand, primarily keeps data in memory for fast access and can be configured to periodically save data to disk. However, Redis is not as durable as Elasticsearch and may lose data in the event of a failure.

  4. Scalability: Elasticsearch is designed to scale horizontally by adding more machines to a cluster. It provides automatic sharding and replication, allowing it to handle large amounts of data and high query volumes. Redis, on the other hand, can scale vertically by adding more memory to a single machine. While Redis supports clustering, it may not scale as easily as Elasticsearch for large datasets.

  5. Full-text Search: Elasticsearch provides powerful full-text search capabilities out of the box. It supports features like stemming, tokenization, and relevance scoring, making it ideal for applications that require advanced search functionalities. Redis, on the other hand, does not have built-in full-text search capabilities and is better suited for simple key-based data retrieval.

  6. Data Types: Elasticsearch supports a wide range of data types, including numeric, string, date, geo, and more. It also provides support for complex data structures and nested objects. Redis, on the other hand, has a limited set of data types, such as strings, hashes, lists, sets, and sorted sets. While Redis offers data structures like lists and sets, it is not as versatile as Elasticsearch in terms of data types.

In summary, Elasticsearch is a powerful search engine and analytics platform that is suitable for handling large amounts of structured and unstructured data. Redis, on the other hand, is a fast in-memory data structure store designed for caching and simple key-value storage.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Elasticsearch, Redis

Rana Usman
Rana Usman

Chief Technology Officer at TechAvanza

Jun 4, 2020

Needs adviceonFirebaseFirebaseElasticsearchElasticsearchAlgoliaAlgolia

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

408k views408k
Comments

Detailed Comparison

Elasticsearch
Elasticsearch
Redis
Redis

Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack).

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

Distributed and Highly Available Search Engine;Multi Tenant with Multi Types;Various set of APIs including RESTful;Clients available in many languages including Java, Python, .NET, C#, Groovy, and more;Document oriented;Reliable, Asynchronous Write Behind for long term persistency;(Near) Real Time Search;Built on top of Apache Lucene;Per operation consistency;Inverted indices with finite state transducers for full-text querying;BKD trees for storing numeric and geo data;Column store for analytics;Compatible with Hadoop using the ES-Hadoop connector;Open Source under Apache 2 and Elastic License
-
Statistics
GitHub Stars
-
GitHub Stars
42
GitHub Forks
-
GitHub Forks
6
Stacks
35.5K
Stacks
61.9K
Followers
27.1K
Followers
46.5K
Votes
1.6K
Votes
3.9K
Pros & Cons
Pros
  • 329
    Powerful api
  • 315
    Great search engine
  • 231
    Open source
  • 214
    Restful
  • 200
    Near real-time search
Cons
  • 7
    Resource hungry
  • 6
    Diffecult to get started
  • 5
    Expensive
  • 4
    Hard to keep stable at large scale
Pros
  • 888
    Performance
  • 542
    Super fast
  • 514
    Ease of use
  • 444
    In-memory cache
  • 324
    Advanced key-value cache
Cons
  • 15
    Cannot query objects directly
  • 3
    No secondary indexes for non-numeric data types
  • 1
    No WAL
Integrations
Kibana
Kibana
Beats
Beats
Logstash
Logstash
No integrations available

What are some alternatives to Elasticsearch, Redis?

Algolia

Algolia

Our mission is to make you a search expert. Push data to our API to make it searchable in real time. Build your dream front end with one of our web or mobile UI libraries. Tune relevance and get analytics right from your dashboard.

Hazelcast

Hazelcast

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

Aerospike

Aerospike

Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.

MemSQL

MemSQL

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

Apache Ignite

Apache Ignite

It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale

Typesense

Typesense

It is an open source, typo tolerant search engine that delivers fast and relevant results out-of-the-box. has been built from scratch to offer a delightful, out-of-the-box search experience. From instant search to autosuggest, to faceted search, it has got you covered.

SAP HANA

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

Amazon CloudSearch

Amazon CloudSearch

Amazon CloudSearch enables you to search large collections of data such as web pages, document files, forum posts, or product information. With a few clicks in the AWS Management Console, you can create a search domain, upload the data you want to make searchable to Amazon CloudSearch, and the search service automatically provisions the required technology resources and deploys a highly tuned search index.

Amazon Elasticsearch Service

Amazon Elasticsearch Service

Amazon Elasticsearch Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time.

Manticore Search

Manticore Search

It is a full-text search engine written in C++ and a fork of Sphinx Search. It's designed to be simple to use, light and fast, while allowing advanced full-text searching. Connectivity is provided via a MySQL compatible protocol or HTTP, making it easy to integrate.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase