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 Mid-sized Companies (51-1,000 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
(26-50 of 75)Companies can't remove reviews or game the system. Here's why
September 07, 2019
Super fast and easy to integrate
We currently use Redis in only one core internal application, however, this application handles around 90% of our company's internet traffic. This application load balances requests intelligently across multiple downstream server clusters. Prior to this, we used to frequently run into bottlenecks at the DB layer when web server scaling alone was insufficient.
The great thing about this is also that each cluster can be running a different version of our application allowing us to maintain a high level of robustness for our larger enterprise customers, while also allowing us to deploy frequently to other clusters that want the bleeding edge. With Redis, being able to determine the right cluster for the right request happens blazing fast.
The great thing about this is also that each cluster can be running a different version of our application allowing us to maintain a high level of robustness for our larger enterprise customers, while also allowing us to deploy frequently to other clusters that want the bleeding edge. With Redis, being able to determine the right cluster for the right request happens blazing fast.
- FAST LOOKUPS. First and foremost, this is the bread and butter of Redis. It is our go-to for any highly performant lookups.
- SCALE OUT. Helps build distributed applications that need to share data across geographies.
- Better GUI clients. At the time of adoption, the choices for UI based clients were poor. Such tools are necessary for tier 1 support personnel who may not be entirely technically savvy.
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.
September 05, 2019
Enterprise performance at a fraction of the price
We use it in our backend DB for our custom CRM platform for Healthcare providers.
- In-memory datasets.
- Computing set intersection.
- Automatic failover.
- Tech support.
- More user forums.
- A Wiki-style support page.
September 05, 2019
Simple yet powerful datastore
We use it as one of our app supporting platforms (Resque & Rails).
- Simple, fast Keystore.
- Reliable.
- Efficient storage.
- Better handling if capacity is reached - sometimes it just crashes our server.
August 27, 2019
Redis is battle-tested
We use Redis as a distributed cache and distributed lock for our microservice environment. We have so many machines performing jobs that it's hard to make sure no task gets dropped or accidentally gets performed twice. And that's where Redis comes in--to store the global state or what jobs have been done in a fast, reliable way.
- Helpful customer support.
- Reasonable pricing.
- Keeps Redis software secure and up-to-date quietly in the background.
- Replies from customer support via could be a little faster. We're on the basic plan, and it can take up to 2 business days--it's not fast enough when your bugs need to be solved right away.
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.
August 27, 2019
Redis is great when you use it correctly.
We use Redis in many capacities. We use it as a caching layer, as a shared heap, as a datastore for lock contention, as a queue, and as a primary datastore. It provides low latency storage that can be used to persist data between web requests. The data structures available allow us to use it to manage contended data in a safe and predictable fashion.
- Fast key value store
- Serializable concurrent usage (by virtue of being single-threaded)
- Wide library support
- Failover is terrifying and its safety guarantees are misleading
- Large sets (> 500k entries) have noticeable performance degradation on what is advertised to be a O(1) query pattern
- Hardware costs are high
August 24, 2019
Wow
Redis is being used across our entire organization. Redis provides us the ability to create distributed locks when requiring atomic operations on DynamoDB.
- Queueing
- Locking
- Speed
- Multi-user authentication
- Built-in SSL support
- Encryption at rest
August 24, 2019
Fan Redis user
We used Redis mainly to cache the database and as a message broker to avoid the hard work on the main server. It's used by our IT department, it's our first choice when we need a broker for messaging or cache data without persistence.
- Cache layer
- Transport layer
- Store data with expiration time
- None, it's perfect for us.
August 23, 2019
Big data architecture with Redis
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
August 12, 2019
Cache in action
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
August 08, 2019
Perfect for caching and expiring data storage
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.
July 17, 2019
Honest hands-on review of Redis
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.
July 17, 2019
Redis might not be the Panacea you are thinking of!
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
June 25, 2019
Redis Review
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.
June 17, 2019
Redis and its CSAT
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
June 01, 2019
Things you can do with Redis
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
May 21, 2019
Redis : Effective cache management solution
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.
May 20, 2019
Redis analysis
We use it as a service. With it, we have developed libraries for rate limiting, ETL job flow coordination, and counters.
- Atomic counters
- Cache colocated with other services that require low latencies
- Automatic memory management
- CLI could be improved
- Configuration management
- Replication and snarfing
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 15, 2019
Overview of Redis
We use Redis as a cache, inter-process communication mechanism and queue system. It is used by our IT team, and it helps us solve technical issues.
- Very high performance
- Low Latency
- High Reliability of data via clustering and disk backups
- Data protocol can be more compact
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.
Used only by engineering for our main production application. We use a Ruby based job system named Sidekiq that uses Redis as its backing store.
- Lots of versatility. We use it as a dumb store for string payloads, but can store a bunch of other data structures also.
- Easy to set up
- Persistence support isn't great. RDB is useless for our case (job system). AOF has *huge* performance issues, particularly when reading the file on startup after a failure.
May 02, 2019
A Perfect Fit
Redis is used across our product offering as a user session store. It allows for very quick access to user session information and has been very reliable, serving our needs well.
- Session storage.
- It's extremely fast.
- Reliable.
- Nothing to suggest. It has fit our needs perfectly.
April 24, 2019
Instant database for instant user experience
Score 10 out of 10
Vetted Review
Verified User
In Anzu technologies Pvt Ltd we used Redis for multiple reasons. We developed a social app which allows the user to bookmark the video and internet content. Performance was an important factor so we implemented user timelines using Redis sorted sets. We implemented the whole notification system using Redis. Our developed micro services architecture is using Redis. Caching was another common challenge where Redis performed very well. We just love Redis.
- Caching
- Instant response
- Easy to use
- Very light footprint
- Nested JSON indexing
- Fragmentation
- Nothing else