TrustRadius Insights for Redis Software are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
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
Redis was used in a project to merge live data from different sources. Then by using Lua scripting we were able to make some further aggregations and data binding for better results. It was essential for us as preparation for next steps. We also used it as session storage manager for some other projects.
Pros
It's fast for key value hashes operations.
Lua Scripting extension is really powerful.
Cons
Single-threaded.
Likelihood to Recommend
Session manager - With in-built expires it's the perfect solution for that scenario. Data binding as we can use its key value architecture to store data from different sources under the same key so they will be automatically matched. And with now previous data structure we can extend for example hashes horizontally. It may be costly to use it as persistent data storage.
VU
Verified User
C-Level Executive in Information Technology (Marketing & Advertising company, 11-50 employees)
We're currently using Redis to support distributed caching and synchronization across our app. Our application runs on multiple servers so ensuring all infrastructure is in sync and key operations are atomic is critical. It's being used by the backend development team in core infrastructure. Redis is well suited to solve this problem as it offers both performance and reliability.
Pros
Atomic operations
Quick Lookups
Widely supported (there are many tools/libraries built over Redis)
Cons
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
Likelihood to Recommend
Redis is a great tool for distributed caching and synchronization/locking in systems with multiple instances. It also works well for non-persistent data that doesn't grow over time, for instance, you might want to use Redis to manage a queue. It's a particularly good choice for pieces of data that are frequently updated.
Conversely, due to price/data I wouldn't recommend Redis for persisted or infrequently accessed data.
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.
Pros
Key-value access, very fast.
Caching - either using hashmaps or simple values.
Cons
The Python package elastic DSL is somehow incomplete.
Moving from a Python client to Redis 2 to Redis 3 is a mess.
Likelihood to Recommend
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.
VU
Verified User
Professional in Information Technology (Information Technology and Services company, 51-200 employees)
We have used Redis in an in-memory key-value store.
Pros
Binary key-value store support
Simple data structures
Very well documented
Cons
Nested use of data structures
GUI tool in better shape
More courses on Redis
Likelihood to Recommend
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.
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.
Pros
Handles huge data without any loss
more number of request at same time
node replication
Cons
Since this is in-memory database but when you use it as persistence DB then pricing will increase.
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!
Pros
Quick and Easy Setup
Fast Performance
Does its job well!
Cons
Setting up a cluster in Redis is a bit confusing and hard for the first time.
Likelihood to Recommend
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.
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.
Pros
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.
Cons
Management console still not quite polished.
No built-in GUI for Debugging keys and values.
Pricing model.
Likelihood to Recommend
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.
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.
Pros
Cacheing APIs - this is where it shines for us
Quick in memory database of key value pairs
The tooling around Redis provides insight into what you are caching and provides easy methods to clear some caches and not all
Cons
New versions of the tooling are not easy to install compared to previous generations
Likelihood to Recommend
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.
VU
Verified User
Manager in Engineering (Marketing and Advertising company, 201-500 employees)