Redis Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
178 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.9 out of 100

Do you work for this company? Manage this listing

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (26-50 of 73)

Anonymous | TrustRadius Reviewer
December 20, 2019

Fast and reliable

Score 9 out of 10
Vetted Review
Verified User
Review Source
Redis is being used across the whole organization as a better cache/message broker service, replacing SQL Server.
  • Caching
  • Message broker
  • Different OSs
So far, the product definitely excels at the services it was designed for. Obviously, it's not a replacement for your typical relational database system.
Read this authenticated review
Anonymous | TrustRadius Reviewer
September 24, 2019

Perfect performing cache

Score 9 out of 10
Vetted Review
Verified User
Review Source
We use it for high-speed cache, data storage for short periods of time, and it is ideal for immediate access to the leaderboard.
  • Speed.
  • Ease of use.
  • Variety of use cases.
  • Support faster SSL access, currently bring performance down by 50% with SSL.
  • Cost - Most providers not cheap.
  • Native support to access search through a variety of data formats.
Redis is well suited for timed caches. Without it, they would require more complex DB solutions. It is very reliable and takes less than 15 lines of code to write a sophisticated solution.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
It is used for the whole organization for caching and performance. We avoid hitting the DB in a factor of more than 100x, at a lower cost.
  • Key-value access, very fast.
  • Caching - either using hashmaps or simple values.
  • The Python package elastic DSL is somehow incomplete.
  • Moving from a Python client to Redis 2 to Redis 3 is a mess.
Redis is good for caching and helps you to avoid hitting the DB. It offers a key-value store where you can put references to objects or temporary values (counters) that will later go to the DB.

Redis isn't as suited for complex objects or serialized data that takes a lot of space. With the milions of users, costs would go way up.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
The R&D department uses Redis as 'in-memory' hot data storage (data storage layer of a machine learning big data architecture).
  • Low latency
  • Support hundreds of connections
  • Significant learning curve
  • Could be costly if not designed right
Good for big data storage architectures.
Less suitable if persistence is required.
Read this authenticated review
Manjeet Kumar | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
First, I would like to clarify that Redis is not being used in production by my organization currently. Right now, I am involved in an R&D project, where I am experimenting on how to induce Redis on various modules. I am planning to use Redis as a cache management solution in our application for now. On successful implementation, we will extend Redis usage to manage other functionality as well.
  • Cache management: Redis is the best solution out there for cache management. It out marked Memcache in latency. Redis gives better flexibility when comes to data storage techniques.
  • For example: Instead of storing objects as serialized strings, we can use a Redis Hash to store an object's fields and values and manage them using a single key.
  • Replication: Redis has the best build in replication feature.
  • For example, It allows slave Redis instances to be exact copies of master instances. The slave will automatically reconnect to the master every time the link breaks and will attempt to be an exact copy of it regardless of what happens to the master.
  • Pub/Sub- It's Publish & Subscribe system of Redis. Where Publish broadcast content to all its subscribers simultaneously. There are various use cases of Pub/Sub. Developers are using it for triggering scripts based on Pub/Sub events. There are various chat ecosystems built on the Pub/Sub module.
  • Redis is super fast but it comes with a cost. Whole dataset resides in RAM. So it can be costly as primary memory is more costly, then secondary ones.
  • Persistence issues: To achieve it, Redis uses a memory dump to create a persistence snapshot, that's cool. But it requires some Linux Kernel tweaking to avoid performance degradation while the Redis server process is forking. This further causes latency.
  • Master-slave structure side effect: Master-slave architecture comes with its own side effects. Please note that there will be only one master with multiple slaves for replication. All writing goes to the master, which creates more load on the master node. So, when the master goes down, the whole architecture does.
Well suited scenarios: Cache management, real-time analysis of events, and leaderboards/counting. Less appropriate scenarios: Persistence and clustering.
Read Manjeet Kumar's full review
Davide Pedranz | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Redis as a distributed cache for many internal tools across the entire organization. Some tool uses Redis as a filter to remove millions of duplicated jobs every day.
  • Really fast.
  • Data model simple to understand.
  • Very simple to use.
  • Support batches of operations to increase performances.
  • Nothing, it just works.
Well suited:
  1. Cache
  2. Filtering out duplicates
  3. Implement rate limits
  4. Store access tokens or revoked credentials
Not suited for:
  1. Storing complex data (go for a traditional database instead)
Read Davide Pedranz's full review
D. Marshall Lemcoe Jr. | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • Key/Value datastore. Redis is incredibly fast when it comes to simple "phone book-style" lookups.
  • Queue orchestration and management when there are many nodes in a system that need to all be on the same page.
  • Dead-simple installation process. It takes about 3 minutes to install Redis and get the service started.
  • I am unable to come up with any legitimate cons, but one thing to note is that Redis, by default, will be installed with no password, leaving it open to the world if the host is not locked-down with a firewall.
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.
Read D. Marshall Lemcoe Jr.'s full review
Adam Stern | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
  • Redis is easy to install and maintain.
  • Redis is very fast, especially with set operations.
  • Redis is cost effective.
  • Clustering, especially with multiple write nodes, can be difficult to configure.
  • Configuring extremely high availability can be difficult.
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.
Read Adam Stern's full review
Shehan Wickramarathne | TrustRadius Reviewer
June 25, 2019

Redis Review

Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Redis to cache huge responses received from 3rd party services in our Backend to Frontend (BFF) layer, to improve performance and loading time in the frontend single page web application. It is used to cache pricing, product data which would stay fixed for a given amount of time. We were able to drastically reduce the loading time of pages in the frontend due to this caching mechanism using Redis.
  • Performance
  • Error resilient
  • Easy to use
  • Learning curve is steep
  • Developing in a local environment can be difficult.
Redis is well suited for quick caching and performance-centric applications.
Read Shehan Wickramarathne's full review
Gunasekar Duraisamy | TrustRadius Reviewer
June 17, 2019

Redis and its CSAT

Score 9 out of 10
Vetted Review
Verified User
Review Source
We have used Redis in an in-memory key-value store.
  • Binary key-value store support
  • Simple data structures
  • Very well documented
  • Nested use of data structures
  • GUI tool in better shape
  • More courses on Redis
It is well is suited as an in-memory key value store for applications which require very little response time. The data can be stored and retrieved from Redis in minimal time when compared to traditional databases. It is not suitable when the data cannot be stored in memory completely.
Read Gunasekar Duraisamy's full review
Joseph Ngugi Muiruri | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Redis has helped us to improve the performance of our database performance by using it as a buffer/cache to the most frequently accessed pieces of data while doing data analytics. It provides us with a faster and simpler way to ship data from the database to the client's computer. It also helps us work with real-time data efficiently and reliably.
  • Excellent performance
  • Scalability
  • Reliability
  • Real-time analytics
  • Few commands
Using Redis to cache our most frequently accessed data was one of the best decisions we ever made.
When it comes to performing analytics, Redis is very efficient at that as well as handling large amounts of data common in the data analytics industry. Redis also acts as a very excellent NoSQL database.
Read Joseph Ngugi Muiruri's full review
Kiran Narasareddy | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Redis is being used by our product engineering team. We use it for caching and as a store for our background processing engine.
  • High-speed access for a database where the size is generally well-known.
  • If you display real-time stock prices, you can use Redis to rapidly get the latest stock price by its key and get it displayed to the user.
  • Support for data structures such as scalars, sets, hashes, and lists.
  • Persistence can impact performance since Redis will use memory dump to create snapshots used for persistence.
  • Redis supports only basic security options. Redis doesn't provide any access control.
  • There is no internal full-text search support and it is difficult to model relationships using Redis.
Well suited for a real-time stock price ticker. Not well suited for eCommerce search.
Read Kiran Narasareddy's full review
Ajmal karuthakantakath | TrustRadius Reviewer
August 12, 2019

Cache in action

Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Redis within a single group and across the enterprise.
  • We used cache data to speed up the processing power.
  • To do intersections of various sets and achieve a high performing solution.
  • To use it as a second-level cache for large data.
  • Luva script is a pain to work on
HTTP sessions, caching, and as DB for a decent size data.
Read Ajmal karuthakantakath's full review
Bagaskara Wisnu Gunawan | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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!
  • Quick and Easy Setup
  • Fast Performance
  • Does its job well!
  • Setting up a cluster in Redis is a bit confusing and hard for the first time.
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.
Read Bagaskara Wisnu Gunawan's full review
prakash ps | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • Session Management
  • Key value pair DB structure
  • High scalability
  • Flash instances
  • Failover Replicas
  • Data Consistency
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.
Read prakash ps's full review
Bob Bennett | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Redis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to leverage it are continually being investigated and identified. It addresses data consistency and concurrency issues and provides amazing speed to what could be slower operations if handled without it.
  • Cache speed
  • Support for high volume of transactions with elegant handling of data sets
  • Ease of use - well structured and easy to implement
  • Price per shard is a bit high but over all there are no issues worth mentioning
  • I've heard some wishing it supported complex queries but this is asking the solution to support operations it wasn't intended for
Redis is well suited for:
  • Big data manipulation
  • Temporal data index structures
  • Distributed solutions
  • Publish/Subscribe model based solutions
Read Bob Bennett's full review
victor pease solano | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
  • It's an incredibly fast database with restrictions. It only has key-value combinations but good anyway.
  • For caching, at the first request-> write to the cache and read from it since DB query is expensive.
  • Persistence, It's like having your session active any time you want.
  • Software-based so the high availability configuration is a little bit tricky.
  • The expire function is manually managed, so keep all your variables well documented.
  • Better to create a Proxy service to deal with Redis values in order to isolate your app from the complexity (not too much anyway).
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.
Read victor pease solano's full review
Guljar Prasad | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • Handles huge data without any loss
  • more number of request at same time
  • node replication
  • Since this is in-memory database but when you use it as persistence DB then pricing will increase.
  • Does not support query like SQL
Read Guljar Prasad's full review
Roberto Luna Rojas | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • High Performance. Compared to other similar technologies Redis is blazing fast.
  • Built-in Data Structures. Redis facilitates the creation of Counts, Leaderboards, & Logs.
  • Scale Out. Other technologies claim to do Active-Active replication but while rebalancing, the Cluster goes irresponsive. With Redis, this does not happen and requests are still being served.
  • Management console still not quite polished.
  • No built-in GUI for Debugging keys and values.
  • Pricing model.
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.
Read Roberto Luna Rojas's full review
Berkant Ipek | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are a small company with a small engineering team. We are actually DevOps based entirely and working actively with Redis as a key-value storage and a backing service for caching. We love its stability, trustworthiness, and speed.
  • Basic Storage
  • Caching
  • Queues
  • Scripting is sometimes cumbersome
Redis is well suited when a multithreaded environment is needed or you're low on memory resources.
Read Berkant Ipek's full review
Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We leverage Redis as our L2 centralized cache to hold frequently accessed data such as user ids, account balances, and other metadata. It is used across our entire organization for various software services and projects. For us, the ease of spinning up an instance and having it "Just work!" is what is appealing. We don't have the luxury of hiring Redis administrators, but since our use case isn't too complex, a hosted version works just fine for us. This should speak to the flexible usability with the product.
  • It's easy to manage.
  • It fits most simple caching use cases.
  • Can be clustered.
  • Highly configurable.
  • Clustering can be easier to set up.
  • Sharing data can be challenging.
It's a great solution for simple and centralized caching layers, and you don't want a lot of overhead. Be sure Redis is the right product for your application's behaviors. Sharing data can be challenging. You will have to think about how to deal with that in the future. I used a hosted Redis version, and although there was noticeable "ping latency" vs a localize instance, the latency was within our acceptable response window.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User
Review Source
Redis is currently being used in silo within my company. Our department was one of the first groups to use it as part of the software modernization initiative.
  • Caching strategy
  • Redis is not a panacea for fast and quick access to the frequently used data. There were times the development team had to go back to JVM cache to achieve the use case.
  • Maintaining Redis as a separate persistence has its price ( in operation and maintenance).
  • HA and DR was a biggest challenge with the widespread adoption of Redis
Don't expect Redis to replace your SQL/ NoSQL persistence layer altogether. It's very tempting to think that Redis can turbo boost your web application to Utopia, but be very judicious in selecting what Redis can do for you. There is always a price to bring an additional component into your ecosystem.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • Simplicity combined with power. The Redis API is very simple to use, but it also excels at handling large amounts of traffic.
  • Redis is scalable and can seamlessly scale outwards to store and retrieve larger amounts of data.
  • Redis has an incredibly strong community and tool suite. There is an ample amount of tutorials and connections, making it a great choice regardless of your tech stack.
  • It would be better if there were some more advanced tooling. It doesn't feel quite as robust as some data storage options.
  • It's unclear how much the core team is doing to advance the product. I'm not a hardcore follower, and there is little news about what is happening.
  • Sometimes things can feel a little too abstracted. I've used it for a long time, but rarely know what is happening underneath the hood.
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.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • Speed: Redis is, generally speaking, very fast. I typically place Redis somewhere within my internal network so the major factor in the speed of retrieving data is the size of the data cached.
  • Configuration: Redis is very configurable to the point where you can utilize it as simply as a single instance running with no backups to a multi-tiered cluster running with permanent storage, data backups, and replication.
  • Documentation: Redis has done a good job of documenting all of its capabilities as well as providing guidance in terms of what client libraries exist to help the developer's application(s) interface with it.
  • I, as a rule, don't use Redis for persistent data, but it would be nice if Redis had an option to persist data to another data source such as MySQL or PostgreSQL.
  • This is more a wish list item than a con but, it would be nice to have the ability to configure Redis as a write-through proxy. This is generally done by having a processor processes write-data to Redis, another process then reads the data from Redis and writes it to a database, and then finally the keys that have been written are flushed out of Redis.
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.
Read this authenticated review
Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Redis provides support for database analysis and integration of many functions and programs. It is mainly used by our backend team and data analyst. It helped us to grow and expand our business a lot. The tools they provide for the system are the best thing for our organization. Our whole organization is fond of using it and is praiseworthy by our whole team. Many projects that we have done are due to Redis.
  • Introduction to new things like sorted list and hyper logs.
  • Speed of deployment for programs.
  • Data structure it has given.
  • Data scaling
  • User interface
Redis supports different kinds of data structure like sorted list, geospatial indexes with radius queries, and streams, etc. It helps us show usable data to our customers.
Read this authenticated review

Feature Scorecard Summary

Performance (66)
9.2
Availability (66)
8.7
Concurrency (65)
8.5
Security (60)
6.8
Scalability (66)
8.6
Data model flexibility (59)
8.0
Deployment model flexibility (59)
8.2

About 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 Features

NoSQL Databases Features
Has featurePerformance
Has featureAvailability
Has featureConcurrency
Has featureSecurity
Has featureScalability
Has featureData model flexibility
Has featureDeployment model flexibility
Additional Features
Has featureIntegrated modules
Has featureActive-Passive Geo Distribution
Has featureCluster Architecture
Has featureLinear Scaling
Has featureDurability
Has featureBackup and Disaster Recovery
Has featureReliability

Redis Screenshots

Redis Video

Redis Downloadables

Redis Integrations

Apache Spark, OpenShift, CData, Pivotal Cloud Foundry

Redis Competitors

Pricing

  • Has featureFree Trial Available?Yes
  • Has featureFree or Freemium Version Available?Yes
  • Has featurePremium Consulting/Integration Services Available?Yes
  • Entry-level set up fee?Optional

Redis Support Options

 Free VersionPaid Version
Phone
Live Chat
Email
Forum/Community
FAQ/Knowledgebase
Social Media
Video Tutorials / Webinar

Redis Technical Details

Deployment Types:On-premise, SaaS
Operating Systems: Windows, Linux, Mac
Mobile Application:Apple iOS, Android, Windows Phone, Blackberry, Mobile Web
Supported Countries:Global
Supported Languages: https://redis.io/clients