Skip to main content
TrustRadius
Redis™*

Redis™*

Overview

What is Redis™*?

Redis is an open source in-memory data structure server and NoSQL database.

Read more
Recent Reviews

TrustRadius Insights

Redis has proven itself to be an invaluable tool in a wide range of use cases. Users have found Redis to be exceptional as an efficient …
Continue reading

Set up & forget

7 out of 10
May 08, 2021
Incentivized
We use it to manage & control user sessions in a Tomcat based web application programmed with Java. It's used in both production and …
Continue reading

Redis Review

9 out of 10
February 03, 2020
Incentivized
Redis has been a vital component in our design, it's usage is mainly for caching API requests, but it also extends to other applications …
Continue reading

Redis is awesome!

9 out of 10
November 23, 2019
Incentivized
We're using Redis in many ways and across different departments in the organization. The most simple use case is to store locks so the …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 7 features
  • Performance (69)
    10.0
    100%
  • Scalability (69)
    9.4
    94%
  • Availability (69)
    9.0
    90%
  • Concurrency (68)
    9.0
    90%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Cloud

$388.00

On Premise
per month

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visithttps://redislabs.com/pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Features

NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

9.2
Avg 8.8
Return to navigation

Product Details

What is Redis™*?

According to the vendor, Redis is an in-memory multi-model database that supports multiple data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability and automatic partitioning with Redis Cluster.

Redis combines in-memory, schema-less design with optimized data structures and versatile modules that adapt to your data needs. The result is an adept, high performance, multi-purpose database that scales easily like a simple key/value data store but delivers sophisticated functionality with great simplicity, according to the vendor.

Redis also enables data persistence and high availability through replication and backups. Redis Enterprise is built from the ground up to serve as a system of record for any application.

*Redis is a trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by TrustRadius is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and TrustRadius.

Redis™* Features

NoSQL Databases Features

  • Supported: Performance
  • Supported: Availability
  • Supported: Concurrency
  • Supported: Security
  • Supported: Scalability
  • Supported: Data model flexibility
  • Supported: Deployment model flexibility

Additional Features

  • Supported: Integrated modules
  • Supported: Active-Passive Geo Distribution
  • Supported: Cluster Architecture
  • Supported: Linear Scaling
  • Supported: Durability
  • Supported: Backup and Disaster Recovery
  • Supported: Reliability

Redis™* Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of

Redis™* Video

Why Redis?

Redis™* Integrations

Redis™* Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationApple iOS, Android, Windows Phone, Blackberry, Mobile Web
Supported CountriesGlobal
Supported Languageshttps://redis.io/clients

Frequently Asked Questions

Redis is an open source in-memory data structure server and NoSQL database.

MongoDB, Amazon ElastiCache, and Couchbase Server are common alternatives for Redis™*.

Reviewers rate Performance highest, with a score of 10.

The most common users of Redis™* are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(224)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Redis has proven itself to be an invaluable tool in a wide range of use cases. Users have found Redis to be exceptional as an efficient caching solution, allowing for the distribution of data and storage of web sessions. This capability has led to significant improvements in performance and reliability, making it a go-to choice for many backend development teams. Additionally, Redis's versatility as a NoSQL key-based database store has made it a preferred option for organizations working alongside other databases like PostgreSQL and Memcache. Its ease of use, stability, and reliability have made it a popular choice across multiple departments within organizations.

Furthermore, Redis has been leveraged in various R&D projects to experiment with its implementation in different modules. Starting with cache management, users have been able to extend its usage to address specific project needs effectively. In these experiments, Redis has served as a traditional in-memory key store warehouse for cache systems with a vast number of items, resulting in substantial latency savings. Its ability to manage distributed queues efficiently has also made Redis an excellent choice for tasks that require multiple worker nodes to subscribe and complete tasks. The flexibility Redis offers by enabling users to store sets of object-based information and lists further improves performance through set operations.

In addition to these use cases, Redis has become synonymous with simplicity and speed when it comes to basic yet fast key-value storage solutions. It has been extensively adopted in organizations, including game studios, where it is used for storing user data, session data, game data, and indexing information. For example, Redis Enterprise has been utilized to support backend systems for casual games by providing sub-millisecond response times and facilitating clustering, sharding, backups, and monitoring.

Moreover, customers have found Redis instrumental in addressing various challenges such as big data processing, handling temporal data, managing session state, and even as a caching service in microservices environments. Its ability to provide data consistency, concurrency management, and high-speed operations has proven invaluable. Additionally, Redis has been a reliable tool for caching solutions in e-commerce storefronts and data visualization applications. Users have reported reduced server load and improved performance as a result of implementing Redis as a cache.

Redis has also found success as a buffer cache, allowing for faster data retrieval and improved overall database performance. Its role in processing queues, calling APIs, and supporting vital organizational workflows has been recognized by customers who rely on its stability and speed. Furthermore, users have implemented Redis across various domains to manage user timelines, build notification systems, and implement microservices architecture

Users recommend the following for Redis:

Consider other cache options before choosing Redis. It is advisable to try out other caching solutions before jumping to Redis, even though it is a great tool for highly distributed caching.

Understand the purpose of Redis in your implementation. It is important to have a clear understanding of how Redis will be used in your specific application. Don't assume that it will work straight out of the box. Evaluate data structures and choose a model that allows for faster query times.

Use Redis for specific use cases. Redis shines in certain areas such as synchronizing states across instances and handling user sessions with Node.js. It can also be a good alternative for relational data when speed is of utmost importance. However, users caution against abusing Redis and recommend using it in a reasonable way.

Overall, users believe that Redis is a valuable tool for fast reliable storage and caching, particularly for enterprise applications. However, they also advise considering other key-value stores depending on the specific use case at hand.

Attribute Ratings

Reviews

(51-75 of 75)
Companies can't remove reviews or game the system. Here's why
Guljar Prasad | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We are using Redis for one of our clients. We wanted to find a way to handle huge amounts of data for every user search and their MySQL was not able to handle it quickly. We were discussing going more toward NoSQL. After more R&D, we chose Redis. Now it is handling data in an excellent way. It's for a travel product where we are searching hotels and flight for queries given by users, and Redis is rocking here.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
In our project (high load web application with 10k+ users) we used Redis as a user session store, as a distributed cache for web front end servers (with PubSub notifications for changes propagation), and for notification service.
Bagaskara Wisnu Gunawan | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is a vital part of our organization as it enables us to process a whole load of queues that our tools have to process. It provides so much value for us since most of our tools require queues to call APIs, etc. We used Redis because of its simplicity of setup and its fast performance. We loved Redis and sure you'd love it too!
Score 10 out of 10
Vetted Review
Verified User
Redis is our primary caching database. We cache most of our intermediate results for backup and scan operations using Redis. Of late, we have also been using it as a message queue. The performance is excellent and features like automatic failover and cluster management are very helpful. All necessary data structures like lists, maps, etc. are supported.
Roberto Luna Rojas | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We are starting to move towards using Redis as our primary storage for performance and simplicity reasons. We have been using it for the last 5 years as a Caching and Session storage mechanism, but last year we started to implement it across multiple services.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We have a country wide application for generation of an Electronic Way bill for the specific consignment/movement of goods from one place to another, either inter-state or intra-state and of value more than INR 50,000, required under the current GST regime in India typically showing the names of the consignor and consignee, the point of origin of the consignment, its destination, and route. We have specifically used Redis for Caching of user profile information used for authentication of the supplier, recipient, and the transporter. Redis has also been used to cache the Items and their Codes. In the future we also propose to use Redis for authentication and session management. The e-Way Bill replaces the Way Bill, which was a physical document and existed during the VAT regime for the movement of goods. The countrywide roll-out of the e-way bill system is targeted to reduce tax evasion with proper invoicing of the goods and to stop the practice of bogus invoicing of goods. It also plays an important part in the tracking of Goods with the use of robust technology like (RFID) Radio Frequency Identification Devices. Redis was implemented as a cache for all transporter data stored on the GSTN (Good and Services Tax Network). When a transporter entered their GSTIN (Goods and Services Tax ID Number) number into the system, their data was fetched from the cache and used to populate the bulk of the e-way bill.
prakash ps | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use redis and recommend for our clients. The key areas Redis outsteps all others are:
1) Scalability
2) Unique and flexible key value db structure
3) They use Ssd Flash for their instances

They also provide session management capabilities to be implemented in any huge projects without much headache. Their db instance also provides a high number of read write per second, which makes it a leader.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is used as a cache layer for our high read data as well as a database layer for write-intensive data. It's used in the entire engineering department as the de-facto caching layer for all services being built. The read and write speeds are unmatched because of the simplicity of the design.
March 27, 2019

Redis Review

Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is being used extensively by our Web/Cloud department, of which I am a part of. We use Redis essentially for cache'ing but we pretty much try to use it for as much as we possibly can. Almost any information retrieval that we can offload to Redis will save as money, as well as reducing our response times. That is, any time we know that our data requirements are simple enough for a key/value setup to suffice, we use Redis - and in my opinion, anywhere we do not do this is a mistake.
victor pease solano | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We used to have most of our web apps accessing our database backend directly, and this was very resource consuming, especially in catalogs and details. This was more critical in our e-commerce storefront. With Redis, we were able to update our webs in order to cache all the queries with resources displayed frequently. In that way, we freed our servers of a huge load. The auto-expire function lets us use the Redis cache and not have to continuously monitor it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Redis for cache storage for data that we need to serve quickly. It is used across the whole organization. It has helped scale up our company and continue to server larger amounts of traffic. Getting data quickly is always a difficult challenge while growing your company, and Redis allows us to serve users quickly and efficiently.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
In our organization, Redis is being used as a temporary cache for ephemeral data. This solves the problem of needing to store cached data in a centralized place that is accessible by multiple devices and can be retrieved quickly. In general, nothing is stored in Redis that can't be reproduced from another resource on demand. For example, if we have a process that creates summaries of data from multiple data sources and is costly or very time consuming, we would cache those results in Redis for an appropriate period of time to make it available to other applications in a timely manner without having to rerun the original process. This reduces the time/cost normally incurred to review that data set.
D. Marshall Lemcoe Jr. | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Our organization uses Redis for two main tasks at our organization. First, Redis is used as a traditional in-memory key/store warehouse for a cache system that contains over 400 million items, on average. Using Redis with modern DDR4 memory, we have seen incredible latency savings when it comes to keystore look-ups. Second, we use Redis to manage a distributed queue, such that numerous worker nodes can subscribe to tasks and complete them in an organized way.
March 19, 2019

Redis Review

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Redis is, at a high-level, an in-memory data store largely setup at a key-value store (although it can persist data to disk, and supports more complex data structures). Redis is generally used as part of a cache layer and has a number of additional use cases that it fills well (messaging and task queues).
March 13, 2019

We love Redis

Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Redis for caching for our APIs. It's been rock solid since we made the switch from Memcached to Redis. Memcached was starting to be problematic for us, so Redis was a natural next choice for our caching needs. Aside from being stable and "just working" the tooling is far superior than other caching services I've used. It can be deployed easily as a docker container as well.
Adam Stern | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are currently using Redis to store sets of object-based information and lists. We query an external system and generate lists in Redis based on the query responses. Because Redis is great at set operations this speeds up the time it takes to make set-based calculations. This Redis cluster supports the a large aspect of the whole application.
December 13, 2018

Redis is goooood!!!

Rahul Chaudhary | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is a basic, but extremely fast, key-value storage. We made a decision to use Redis because our use case didn't require a full blown database. We needed something to hold the data temporarily and loss of that data wouldn't lead to any issues. Redis was perfectly fitting our use case, and since then we are a bunch of happy Redis users.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I used Redis in the context of an Airline company middleware implementation. At that time, we were looking for an efficient caching solution with the possibility to distribute data across nodes (i.e. sort of data grid without the complexity of a data grid).
Redis allowed us to build very fast a small cluster of nodes (4) serving as a cache for storing web sessions.
Because of additional features of Redis (pub/sub, in memory Keystore), Redis was also identified as non-critical storage for some data.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Redis was used internally by software development teams as part of a web application stack. Each development team was free to use alternate technologies, including none at all, but for teams with performance requirements, Redis was chosen to provide an in memory cache layer buffering web requests from directly hitting the database.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We have tried using Redis to move from a relational DB to a key-value logic. In view of the use of a DB not SQL, it is certainly performant even if unlike other SQLs, it requires a little more reasoning about the proper analysis of the key value to be used and the way in which they are then interrogated.
Nitin Pasumarthy | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Redis for low latency repetitive point queries. To break it down:
  • Low latency: As it is in memory, saves on I/O
  • Repetitive: As part of ETL we use it to address resolution, .i.e. given an address, find a representative lat long for it. As millions of rows are ETLed every day, there is high chance that they repeat. Having in-memory helps again
  • Point queries: WHERE age BETWEEN 10 and 30 is a range query and WHERE age = 15 is a point query. We use it only for point queries
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We mostly use Redis as a cache for data flowing through a data processing pipeline. When we have surges of activity, we rely on redis to alleviate the stress on our pipeline and ensure that no messages are lost. We also use some of the features in Redis to synchronize our services across several servers.
Adam Lauer | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use redis as a cheap, available, quick storage option. Think of it as a cache on steroids. It lets us store mass amounts of data and access it quickly. The best part is the access cost is not per demand, you are just paying what is hosting the redis clusters.
Return to navigation