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
Bagaskara Wisnu Gunawan | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
It simply has a lot of use cases, but, for our case, we always use Redis for our Laravel queue driver and also for our application's cache driver because it runs so fast and we just couldn't ignore that. We use Redis for dispatch Jobs, storing the cache, working on queues, etc.
Roberto Luna Rojas | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is well suited for applications with well-defined data usage within the NoSQL space, that is counters, queues, leaderboards, time-based, key-value hashes, or for anything that requires many secondary indexes. Still, for a tabular view, a relational DB would make more sense. In the case of full-blown JSON lookup, maybe other NoSQLs could perform as well as Redis.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Redis has its advantages in the 3Vs viz. Volume – Scale from TB to Zeta Bytes (Billion TB), Variety – Manages the complexity of data in many different structures –Ranging from relational, to logs, to raw text and Velocity –Streaming data, large volume of transactions/requests and data movement. Redis is ideally suited for data caching, authentication and session management. Redis' advantage is in handling Scale, Performance and Flexibility (schema-less). It has also has its advantages in Replication of every data element to another node and Sharding and Partitioning so as to Distribute data across nodes in a "share nothing" approach.
prakash ps | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is particularly suited when you want to mesh millions of data and get a unique statistics or a child dataset out of it. Then Redis is the only viable product with the highest number of read and write per second. It increases my speed drastically so that I am able to put 10k records per second and successfully retrieve at same speed.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Good for key value storage. Simple as that. If you need something that has relational data or need more complex data structures, don't use Redis.
If you need something that can be written and read by multiple services, that is as fast as possible, use Redis. The simplicity is its biggest strength, and making it more complex will just ruin the product.
victor pease solano | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Redis is a specialized key-value store, so it's best suited for session variables storage and cache'ing. Redis helps you identify database queries that are repeated exactly the same (for instance, combo lists, product catalogs, configurations, etc).

Redis is atomic, that means you don't have to deal with variables to being blocked to ensure concurrency. So it's great for dashboards, leaderboards, and apps like that.

Redis is not a common database, so don't use it as your repository for data entry or visualization. Yes, it's fast but not that way.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is well suited for any startup or larger company that wants to cache data and scale it out seamlessly. Cacheing is needed when you have data that is frequently accessed or when your queries are expensive. Redis allows you to store objects in memory making it fast and efficient to access them and server the data to large amounts of users without clogging up your server.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is well suited for storage of ephemeral data that could be used by multiple processes. For example, a multi-server website that sits behind a load balancer could use Redis to store session information that might typically be stored on the filesystem. This would allow all the website nodes to share session information without having to resort to sticky sessions.

I generally try to avoid using Redis as a primary data source for critical data.
D. Marshall Lemcoe Jr. | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is the perfect tool if you are looking to increase the speed of a key/value datastore or cache, as well as centralizing your queue management tasks to a dead-simple and incredibly fast database.

That said, it is not well-suited to tasks that have historically been reserved for relational datastores like MySQL or Postgres. Redis lacks relational database features and does not have a dynamic language like SQL to interact with.
March 19, 2019

Redis Review

Score 9 out of 10
Vetted Review
Verified User
Incentivized
For caching, task queues, and messaging, Redis is amongst the best implementation choices. Redis shines when very high throughput is required and very low query times are a necessity. Redis is also a great choice for storing data that can be automatically removed once it expires and should be stored somewhere else. While it is a data structure store, it is not a good choice for highly structured data that should be written to a disk instead (where a traditional RDBMS or NoSQL option is likely a better choice).
March 13, 2019

We love Redis

Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis provides a great caching layer plain and simple. It's rock solid and just works. I'm not sure if my Redis instances have ever gone down.

I'd highly recommend it for caching or in memory key values stores. I'd consider other options if you have to store your data long term.
Adam Stern | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Redis is great at fast operations, especially set-based operations. It is great as an object storage mechanism, such as a cache server or a fast key-value object store. Redis is easily installed and maintained, and setting up clustered instances isn't too terrible. Because the basic installation is open source, it is easy to experiment with before deciding to go with Redis long term.
December 13, 2018

Redis is goooood!!!

Rahul Chaudhary | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is extremely well suited for storing key-value kind of data. Flat and static values are around which they are built. There is no headache of indexing, or maintaining formats like other databases have.

I can also vouch for Redis's pub/sub notification. You can basically set expiration or event hooks around your keys, and Redis will trigger a notification for those events.

But Redis is ill-suited for treating it as a proper database. For instance, this is not a replacement for elasticsearch or mongo.

To assess if you need Redis, in my opinion, just think if you need to query values. If yes, don't use redis. If you are only concerned with key operations, then go with Redis.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Redis fits perfectly when the cache is required or when fast data access is a criterion. With the community edition, we can build very fast and efficient cluster of data nodes with adequate persistent policy.

I don't recommend Redis if you are looking for something else than a key/value store. Even if Redis claims to be a "data structure server", you might face limitations while dealing with other data structures.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Redis is great for application cache, internet cache, sharing sessions across stateless web servers. It also works well as a serializing channel for stream data. It has a pub-sub layer as well, which can be used to facilitate peer to peer data sharing. Because it's built as an in-memory store, it is not suitable for data durability.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
If you want to increase your database queries changing from SQL to Redis probably you can optimize your performance using in-memory cached by Redis, doing this you can have a better workload on SQL servers but you have to configure correctly your complete infrastructure. Furthermore, you need a little bit of time to test your calls with a stress test.
Nitin Pasumarthy | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Good for:
  • Low latency queries are a must
  • Frequent point queries as it is a key-value store
  • Use awesome Redis Modules (Redis Search, Redis Neural Net, Redis ML, Redis-Secondary, Redis Graph)
Not suitable for (as far as I know):
  • When values are complex objects and not simple data structures. Document stores are better for those work loads
  • Huge data and not feasible (due to budget constraints) to scale up RAM
Score 10 out of 10
Vetted Review
Verified User
Incentivized
For anything that requires a cache, redis has been a great option for me for several years. It can easily handle a huge volume of requests, making it a fantastic way to speed up a popular web application, for example. Being able to automatically expire entries after a certain amount of time helps reduce load caused by complex calculations or queries that use other data sources. It's simply fantastic.
Adam Lauer | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
This is best for needing to access data at a high volume quickly at a low cost. This is not the best option if you need high durability of the data and cannot suffer any data loss. Redis is perfect for key-value situations of data including a key being a hash and the value being a huge json object. It is not good when you need a more relational schema.
Return to navigation