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 …
Redis™*
Redis™*
Starting at $388 per month
View PricingOverview
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
Top Rated
2020
Popular Features
View all 7 featuresPerformance (69)
10.0
100%
Scalability (69)
9.1
91%
Availability (69)
9.0
90%
Concurrency (68)
9.0
90%
Video Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Redis™*, and make your voice heard!
Pricing
View all pricingCloud
$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 Scorecard
NoSQL Databases
9.2
92%
Product Details
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™* Downloadables
Redis™* Integrations
- Apache Spark
- Red Hat OpenShift
- CData
- Pivotal Cloud Foundry
Redis™* Competitors
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 |
Comparisons
View all alternatives
Frequently Asked Questions
What is Redis™*?
Redis is an open source in-memory data structure server and NoSQL database.
What are Redis™*'s top competitors?
What is Redis™*'s best feature?
Reviewers rate Performance highest, with a score of 10.
Who uses Redis™*?
The most common users of Redis™* are from Mid-sized Companies (51-1,000 employees) and the Computer Software industry.
Reviews and Ratings
(211)
Reviews
(1-25 of 75)- Popular Filters
Companies can't remove reviews or game the system. Here's why
June 25, 2021
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 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
May 12, 2021
Best open-source caching database
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.
- 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.
- 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.
May 08, 2021
Set up & forget
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.
- 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.
- 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.
February 17, 2021
Redis is THE solution to all your caching problems
Redis is used as our primary cache for our application to help reduce response time and improve user experience. By caching read intensive data in Redis, this also helps to reduce load on our database.
- Great performance for reading data
- Easy to set up and work with
- Great support for many different types of data structure
- Lacking monitoring and administration tools
- System resource consumption as you scale up
April 07, 2020
Great in-memory database solution
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.
We also used it as session storage manager for some other projects.
- It's fast for key value hashes operations.
- Lua Scripting extension is really powerful.
- Single-threaded.
April 06, 2020
Redis is a great product offering from Amazon
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.
- 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.
- 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.
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.
February 03, 2020
Redis Review
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.
- Latency.
- In-memory.
- Ease of use.
- Open source licensing was ambiguous.
January 07, 2020
Redis Solves many application caching problems.
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.
- Application data caching.
- Session data caching.
- Managing cache misses better.
December 20, 2019
Fast and reliable
Redis is being used across the whole organization as a better cache/message broker service, replacing SQL Server.
- Caching
- Message broker
- Different OSs
November 26, 2019
Best DB for a gaming company willing to scale overnight
Redis is used across all the organization. It is used by our main games to store user data, session data, game data, and indexing some information related to it.
Having backend systems that support casual games, like Trivia Crack, must support instant virtualization and big spikes that can happen during holidays, Christmas, and so on. Consequently, it is important to have a sub-millisecond database to be able to increase the requests rate very rapidly.
Having backend systems that support casual games, like Trivia Crack, must support instant virtualization and big spikes that can happen during holidays, Christmas, and so on. Consequently, it is important to have a sub-millisecond database to be able to increase the requests rate very rapidly.
- Answer requests at sub-millisecond latency: by having all the data in memory, the latency has no comparison to other disk based DBs.
- Simplicity: it is incredibly simple and straightforward to use. You can download Redis and start using it during the next five minutes.
- Reliable & scalable: when working with a cluster (and if you have a proper sharding strategy), your DB can scale to pretty high numbers and not to die in the middle of any spike.
- Cost: by having all the data in memory, it can be very expensive. There should be an option for having some data stored on disk, at least initially (and with the tradeoff of some higher latency).
- Lack of some basic permissions: there should be a way of having a user with restricted commands (i.e.: no keys *, now write commands, etc).
- Multi-module available on the same Redis instance (as far as I know, this is not possible yet).
November 23, 2019
Redis is awesome!
We're using Redis in many ways and across different departments in the organization. The most simple use case is to store locks so the backend services can reject duplicated API requests. A little more advanced use case is to use it as a buffer for queues of messages or requests. We're also exploring ways to use the new Graph type to support Data Science models in development.
- Redis has many data types that suit a variety of use cases such as caching, message queues, graphs.
- Redis is an open-sourced tool with a growing community, as well as 3rd party support (Amazon managed version) if you need additional help with the set-up.
- Both the clients and the command line tool are easy to use and well-documented.
- Scaling has always been an issue with Redis. Routing to shards is not automatic.
- There's no GUI for managing the keys and values stored in Redis. The command-line tool is useful but not friendly to non-engineering users.
- The data types as in data structures have many choices, but inside of the key-value pair, the content is always stored as a string.
Redis is being used as our main nonSQL database store. We run PostgreSQL as the main relational data store, Our entire platform used within the business unit utilizes Redis and is also customer facing. The stability, reliability and scalability are great and it's also easy to easy to set up and implement.
- Great reliability and great fail over capabilities
- Easy to set up, implement and deploy
- Can scale as you grow
- Backups to AWS S3 are supported and are very easy to set up
- Better UI interface for less technical support personnel
- Wish Reids had a Chat support option
- Better documentation in a wiki format
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 21, 2019
Redis is Awesome
Redis is being used as our primary NoSQL key-based database store. In the specific platform that Redis is being used the most, we have PostgreSQL as the main relational data store, Memcache for expiring key-based caching and Redis. The entire platform used within the business unit utilizes Redis but other departments are starting to use it as well given the ease of use, stability, and reliability.
- Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
- Reliable. With a proper multi-node configuration, it can handle failover instantly.
- Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
- Fast. We process tens of thousands of RPS and it doesn't skip a beat.
- Autoscale. We've used Redis at RedisLabs and currently on AWS with ElastiCache plus previously I've self-hosted it and there are no real options for "serverless" or an operating model whereby I'm using only the resources needed to handle my current volume, instead, everything is provisioned and sized to your highest throughput needs. For us, that's only a few hours a day where we're at our peak, the other 16 hours could run smaller hardware but the system doesn't autoscale up/down seamlessly on any of the platform providers.
- Management console. Some systems such as Riak have a built-in GUI for ops or Mongo runs their own Compass product but Redis seems to entirely rely on other OSS solutions, which is great, but having a built-in tool that's lock-step with the released versions would ease any quick troubleshooting that CLI-challenged ops teams could utilize.
- Redis replication is asynchronous. Therefore, when a primary cluster fails over to a replica, a small amount of data might be lost due to replication lag.
September 19, 2019
If you need lots of user sessions, this is the product to use
Redis is used by our organization to deliver schedules to the users of livestreams and playlists. We needed something that could deliver very high requests per second and also allow us database updates without impact to our customers. This has been accomplished with Redis.
- The system is very reliable. The only times we had issues was when we hit database capacity limits.
- There is continuing development on the technology (like Redis streams) that make it an even more attractive technology.
- For systems that require many concurrent users, like several million watching the Super Bowl on their connected devices, it works and it works well.
- None that I can think of
September 17, 2019
Redis is a great solution for any company that wants fast development and good performance
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.
September 16, 2019
Get a cache server on steroids with Redis and get rid of those Memcached instances
We use Redis as a Cache DB in a microservices environment to store auth tokens, temporary data and sync flags to coordinate processes that are handled by multiple parties asynchronously.
The main problem it solves for us is to need to have a high-performance cache that also provides data persistence so we can restart instances and deploy new ones without losing data in the middle. This is very important for us because of the problem we're tackling. In the case of auth tokens, we don't want to make all users log in again after we restart an instance because the memory got cleared. The same applies for the sync flags that our processes depend on to complete.
The main problem it solves for us is to need to have a high-performance cache that also provides data persistence so we can restart instances and deploy new ones without losing data in the middle. This is very important for us because of the problem we're tackling. In the case of auth tokens, we don't want to make all users log in again after we restart an instance because the memory got cleared. The same applies for the sync flags that our processes depend on to complete.
- High performance. Redis is FAST, really fast.
- Data persistence. Having this feature was the main reason we chose Redis over Memcached.
- Clustering. Distributing data between multiple instances is easy to do with Redis.
- Data types. It isn't normal to have native data types supported on cache servers, but Redis covers many areas for this use case.
- The data type collections aren't extensive and can fall short for some needs.
- Single-threaded. Redis doesn't support multi-threading, so it won't benefit from multi-core CPUs. Instead, you need to deploy several single-core instances to scale horizontally. While this is a design decision, it may be a downside on some infrastructures.
- Lack of UI. A visual UI can be a downer for some users.
September 14, 2019
Redis Rocks
We use Redis as a cache for our Django application, and as the result storage for Celery, our distributed task runner.
- Simple
- Fast
- Has a variety of data types
- Transaction support
- Automatic command when a connection closes
- Negative acknowledgement support in streams
September 11, 2019
Redis is the best cache database on the market
We use Redis to store data such as ID sessions, card tokens. We have a cluster with three servers in three different environments, and it's working very well.
- Very scalable.
- High performance.
- Easy to use.
- Management tool could be better.
- Books in Spanish.
September 11, 2019
The Redis Imperative
Redis is used for transnational processing and scoring of customer data models for pub/sub-distribution to other models of data.
- Redis provides the ability to score data quickly.
- Redis provides the ability to distribute this info in a fast manner.
- Redis provides an alternative method for data retrieval which lessens the load on the database access.
- Greater emphasis on Pub/Sub capabilities more in line with Kafka.
September 10, 2019
Redis is the backbone of our ephemeral data, from web page caching to session storage.
We use Redis to run frontend caching, sessions and backend value store systems for our main web property. We are big supporters of the community and love watching it evolve over time. We've been early adopters in the NoSQL movement starting with Mongo and Couch. We're still using Redis, although we can't say the same for the others.
- Key value storage
- Session and Cookie management
- Frontend caching
- Third-party library support sometimes lags
- Weak type support
- Everything is in memory, so you need lots of RAM