Blazing performance, excellent stability, and really nothing to dislike make Redis a must look at solution
Redis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to …
Starting at $388 per month
View PricingOverview
What is Redis™*?
Redis is an open source in-memory data structure server and NoSQL database.
Recent 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
- Performance (69)10.0100%
- Scalability (69)9.494%
- Availability (69)9.090%
- Concurrency (68)9.090%
Reviewer Pros & Cons
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
Features
Return to navigation
Product Details
- About
- Integrations
- Competitors
- Tech Details
- Downloadables
- FAQs
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
Redis™* Video
Why Redis?
Redis™* Integrations
- Apache Spark
- Red Hat OpenShift
- CData
- Pivotal Cloud Foundry
Redis™* Competitors
Redis™* Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Linux, Mac |
| Mobile Application | Apple iOS, Android, Windows Phone, Blackberry, Mobile Web |
| Supported Countries | Global |
| Supported Languages | https://redis.io/clients |
Redis™* Downloadables
Frequently Asked Questions
Redis is an open source in-memory data structure server and NoSQL database.
Reviewers rate Performance highest, with a score of 10.
The most common users of Redis™* are from Small Businesses (1-50 employees).
Comparisons
Compare with
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!
- Business Problems Solved
- Recommendations
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
(1-16 of 16)Companies can't remove reviews or game the system. Here's why
February 18, 2020
REDIS great as K/V cache
[It's being used as a] Caching service for quick key lookups.
- Quick key lookups.
- Distribution of data is easy and reliable.
- Almost HA.
- HA automatic failover for master and promoting slave on own.
- Doesn't handle 1M r/s sadly.
- Cross DC replication not so great.
October 14, 2019
Improve performance at a reduced cost
We use Redis in our back end messaging platform for database, cache synchronization functions. Redis is being used throughout our entire organization and is the basis for our EMR messaging platform.
- Great fail over capabilities for optimal up time
- Very easy to set up and get running
- Create backups to AWS S3
- Clustering for greater performance is very easy
- Able to scale is easy to set up and can build with your needs
- Complete data sets tend to have some difficulty. But that's mostly on the type of code you're running
- Only one module can be active at one time. Wish you could run multiple
October 08, 2019
Gets the job done!
Redis Enterprise helps us by making clustering, sharding, backups and some more very easy to set-up, control, and monitor. It's quite nice being able to sleep at night knowing that despite all your database is on volatile memory (RAM) or a hybrid solution (Redis on Flash), and still have the information clustered, sharded, replicated, and constantly being backed up, with just a few clicks. The support is really great, and the ease of use and set-up are also big selling points.
- Ease of use and set-up.
- Clustering and sharding.
- Automated backups to remote storage (S3).
- The documentation grows quite fast (200+ commands), perhaps they should have a most-used ranking.
- Redis modules (Bloom, JSON, Search) are great, but only one can be active at a time.
September 25, 2019
Perfect performing cache
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.
September 24, 2019
Redis, a fast, reliable and well supported data storage system
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.
- Atomic operations
- Quick Lookups
- Widely supported (there are many tools/libraries built over Redis)
- 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.
September 06, 2019
Redis Review
Redis is being used as a cache for real-time locations. It serves the last known location of users sharing their location with other users in real-time, thus being an essential part of our organization.
- Storing geolocations - Redis has built-in geolocation storage capabilities, thus saving us the time of developing the logic ourselves.
- Serving fast info for real-time apps - To anyone who works with real-time applications, fast information is the basis of good user experiences.
- I think the documentation could improve. It's not always clear, especially for engineers that are new on Redis.
- Redislabs admin interface could use a tune-up, maybe being more informative and with a better UI.
- I think the main cons I see in Redis could be that it may be a bit too obscure to new users.
August 27, 2019
Reduced costs
Our development team uses it extensively.
- Speeds up database searches.
- Cloud-based without the need for on-prem.
- High availability.
- Support needs to be better, with chat support as an option.
- Training material for new hire dev-ops.
- Wiki-type documentation.
We're using Redis in our development department, as a layer on top of regular databases (MongoDB, MySQL), as cache, and for other critical data storage.
- The main point: speed.
- Easy to use and integrate with the rest of the components of our system.
- Full-text search support
- GUI tools
- Pricing
May 09, 2019
Redis: the best cache store you can get!
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.
April 19, 2019
Redis makes your application super fast.
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
April 19, 2019
Performant In-Memory Database
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.
April 19, 2019
Redis is the DB you didn't know you need.
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.
April 17, 2019
Our experience with Redis Enterprise
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.
- 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.
- 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.
March 21, 2019
Redis is a hammer in search of a nail.
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.
December 13, 2018
Redis is goooood!!!
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.
- Being a non-SQL database, it does not require any structure. Perfect for unstructured data like key-value pairs.
- Redis is extremely fault tolerant. As soon as we write a record, it gets saved to the disk, without any performance issues.
- Redis is very lightweight. In docker it takes less than 30MB, so it is so easy to run multiple containers in cluster without taking too much power.
- Redis has a very good query API, and they are in their website each operation is clearly mentioned with its time complexity. This gives you a clear picture of performance. We didn't in fact do any performance testing because we trusted their site with all the information.
- Redis has a very strong community around it. We have never found an issue for which a solution didn't exist beforehand.
- A cluster in Redis was a little hard to understand and deploy, but this is a one time thing to learn, no worries.
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
- When dataset is small enough to fit in-memory and get full benefits of reduced I/O
- Need of rich data structures for complex querying
- Speed of in-memory store and durability by disk at the same time
- Declarative querying like SQL
- Tools for monitoring and identifying performance bottlenecks
- Key schema design can be tricky and heavily impacts the performance (leading to key scans)