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 is used as cache storage in our data visualization application where response time is key. We use Redis for some of the flag features in a system with more than 20,000 internal users. This in-memory database helped to solve many of the use cases we've had on our product like user based caching, realtime analytical operations on one time fetched results.
Pros
A modern key-value store in-memory database.
Redis [is thorough] and details user documentation.
Data distribution on a multi-tenant cluster is easy and reliable.
Cons
It lacks support for datatypes that are available on other products.
Making it work with Celery is a bit hard and sometime it's not reliable.
Lacks better UI like other systems.
Likelihood to Recommend
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
VU
Verified User
Engineer in Engineering (Internet company, 5001-10,000 employees)
We use it to manage & control user sessions in a Tomcat based web application programmed with Java. It's used in both production and testing & development environments in this certain application's server backend, but only the software development department actually understands & manages it. It solves the case to keep users logged in to the application and also invalidates the sessions when requested or automatically if they expire.
Pros
Has been working well for storing user sessions.
No need for maintenance operations. Once it's set up has been working flawlessly.
Many configuration options, little programming required.
Cons
The actual database structure is difficult to understand.
Only command line application available for free. Difficult to use.
Seems to have some encoding issues when inspecting data directly with CLI app.
Likelihood to Recommend
It is well suited when a web application needs to store any kind of user sessions. It works both for storing logged in user sessions but also for non authenticated users. User sessions are temporary; however, for storing permanent data that needs to be retained across sessions it is not appropriate because Redis is an in-memory database.
VU
Verified User
Employee in Information Technology (Computer Software company, 1001-5000 employees)
Our organization uses data a lot. It is essential that we deal with a huge set of data and in a quick and timely fashion. Our data services in order to achieve this, we use Amazon's Redis cache. It's been working great for us and we have been using Redis for 1.5 years now. It is reliable and helps speed up our services by at least 40% and reduces the DB calls.
Pros
As with other service offerings from Amazon, Redis is fully managed as well and eliminates a lot of burden on our team.
It's easy to get hold of all the metrics as it is integrated with Cloudwatch.
Very quick and easy to deploy and configure the Redis services into our environment.
Cons
It becomes expensive over time and need to keep a close watch on the usage.
If the instance goes down, there is no backup preserved.
Likelihood to Recommend
Redis works great in our data services applications. Very easy to spin off and configure Redis and link it with our services. We have saved a lot of database downtime as we started using Redis. We now access the information directly from Redis cache instead of hitting the database for every information. We had to write a caching mechanism that suites our needs. We refresh the cache on a timely basis to make sure it has the latest data from the database.
VU
Verified User
Engineer in Engineering (Financial Services company, 5001-10,000 employees)
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 such as rate limiting and pub-sub mechanism.
Pros
Latency.
In-memory.
Ease of use.
Cons
Open source licensing was ambiguous.
Likelihood to Recommend
Redis is well suited for in-memory caching, API caching, and rate-limiting.
VU
Verified User
Engineer in Engineering (Computer Software company, 1001-5000 employees)
We used Redis for application data caching. Redis is used by more than one department and is an enterprise standard offering. We have since moved away from Redis as we were able to simplify our architecture given our more powerful database servers after our latest tech refresh. When we were using Redis, our application response times were too slow for certain transactions so we cached the data to improve performance. There are other use cases that we considered like caching of session data. Again our goal was to simplify our architecture and Redis was one of the products we eliminated, not because it wasn't a good product but because we no longer needed it for our application.
Pros
Application data caching.
Session data caching.
Cons
Managing cache misses better.
Likelihood to Recommend
I think Redis is a great product. Our problem was we were using too many different products when we could have been just using one. We had Redis for application data caching, we were using Xtreme Scale to cache session data, when in fact Redis could have handled both. The decision was made to stick with Xtreme Scale but honestly I would have preferred to stay with Redis. Redis handles application data caching well. We had some issues with cache misses, but I think that was more of what we did and less of what Redis did (or didn't do). That being said, after some recoding, we had no issues. I think that the Redis product could be little easier to use there but again, it was probably a learning curve item for us and not so much the product.
Redis is being used across the whole organization as a better cache/message broker service, replacing SQL Server.
Pros
Caching
Message broker
Cons
Different OSs
Likelihood to Recommend
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.
VU
Verified User
Professional in Information Technology (Financial Services company, 1001-5000 employees)
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.
Pros
Caching strategy
Cons
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
Likelihood to Recommend
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.
VU
Verified User
Director in Information Technology (Health, Wellness and Fitness company, 10,001+ employees)
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.
Pros
Automatic failover
Exhaustive set of data structures
If you want some simple messaging service, Redis pub/sub is excellent.
Cons
It's difficult to understand the use cases initially. The website should talk about "why Redis" first, then "how".
Likelihood to Recommend
Caching is its primary use case. If you need lightweight pub/sub support, then Redis is good.
VU
Verified User
Engineer in Engineering (Computer Software company, 1001-5000 employees)
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.
Pros
Adoption of Redis, gave us the ability to realize our goal of digitally transforming the process of filing returns, generating bills, and tracking the movement of goods across states.
Using Redis Enterprise, we were able to reduce the time it took to generate an e-way bill by more than 85%. Just as important, we were able to dramatically reduce the burden on our SQL database and API calls.
Highly available persistent caching solution recognized for its seamless compatibility with Microsoft SQL Server and Consistent end-to-end response times below 40ms.
Flexible data structures and commands for efficient application in use cases beyond caching.
Cons
Session management is currently being handled in memory by our SQL server, but as the number of concurrent sessions during peak times moves from today’s average of 50,000 to an expected 100,000, we’ll need to implement more efficient session and authentication management likely within Redis Enterprise.
Manage the complexity of data in many different structures ranging from relational, to logs, to raw text. Handling of Streaming data, large volume of transactions/requests and data movement.
The functionalities like Joins (inner/outer join), Set operations (Union/Intersect/Minus), Transactions, Full ANSI SQL support, Constraints (like RDBMS) are not easily supported.
Likelihood to Recommend
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.
VU
Verified User
Director in Finance and Accounting (Government Administration company, 1001-5000 employees)
