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
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
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.
84.28571428571429%
8.4
- Using Redis gives us the chance to create new products.
We divide projects between Redis and Elasticsearch Service. In some parts or modules one of these two databases fit better than the other.
3
In our organization Redis is mainly used by developers.
3
Developers that have basic knowledge about AWS Cloud
- Session storage
- Real data binding/matching
- Data binding
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.
64.28571428571429%
6.4
- Redis has helped to save time by reducing our usage of data access methods on our server.
No
- Price
- Product Usability
- Product Reputation
We selected Redis over Memcached because Redis provided more client processing options and better server handling with its computations.
3
Database Mangers, Developers
1
Architect
- Scoring data.
- Distributing data changes.
- keeping non-transnational items from the database.
- To replace Firebase
- By expanding more on the Pub/Sub capabilities of Redis.
I would start by defining the entire use case and future product development cycle.
- Implemented in-house
No
Change management was minimal
- Whitelisting of the AWS IP addresses.
No
No
We had some issues with the connection to the Redis server and were able to resolve it with the team in a quick and efficient manner.
- Key store
- Key count
- Zcount
- Hash retrieval through Python.
- Connecting javascript clients and retrieving with promises.
No
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
72.85714285714286%
7.3
- The productivity increased
- Needs more security aspects
- Performance has improved tremendously
No
- Price
- Product Features
- Product Reputation
- Third-party Reviews
We want to compare Redis with Ignite.
1
We have not started using redis. I am planning to introduce redis in my organization. It will very helpful if redis provides any demo videos. My company is known for its standard in the payment industry. We make Point of Sale machines of high quality and also commerce applications
I think one must have a strong understanding of redis basic data structure and its functions. Also, people should keep updating their skills based on the newer versions of redis. This help redis increase in more range and also increase productivity in the company. This is a win-win situation for both the parties
- in-memory cache, where we store our data
- it can be very helpful in key management
- also storing the batch data
April 17, 2019
Redis on high scalability world
We use redis and recommend for our clients. The key areas Redis outsteps all others are:
1) Scalability
2) Unique and flexible key value db structure
3) They use Ssd Flash for their instances
They also provide session management capabilities to be implemented in any huge projects without much headache. Their db instance also provides a high number of read write per second, which makes it a leader.
1) Scalability
2) Unique and flexible key value db structure
3) They use Ssd Flash for their instances
They also provide session management capabilities to be implemented in any huge projects without much headache. Their db instance also provides a high number of read write per second, which makes it a leader.
- Session Management
- Key value pair DB structure
- High scalability
- Flash instances
- Failover Replicas
- Data Consistency
- It increased my speed of meshing.
- It increased my user experience by stream-less rendering.
- It created huge impact in my metasearch, my basic income has increased by 120% in last 45 days.
Redis was initially in the list of competitors like Aerospike, Cassandra, MongoDB.The major point that outset all others is that it provides a number of read and writes to the database that no one can match. Another major factor is Redis really knows the basic components that we need these days, e.g. we can take mpas for geolocation, and they provide a rich set of datatypes that becomes handy.
75
100
- key value
- streams
- hash
- nothing
No
March 30, 2018
Redis - memory is the new disk
I used Redis in the context of an Airline company middleware implementation. At that time, we were looking for an efficient caching solution with the possibility to distribute data across nodes (i.e. sort of data grid without the complexity of a data grid).
Redis allowed us to build very fast a small cluster of nodes (4) serving as a cache for storing web sessions.
Because of additional features of Redis (pub/sub, in memory Keystore), Redis was also identified as non-critical storage for some data.
Redis allowed us to build very fast a small cluster of nodes (4) serving as a cache for storing web sessions.
Because of additional features of Redis (pub/sub, in memory Keystore), Redis was also identified as non-critical storage for some data.
- Redis is easy to learn and concepts are very simple. It's an in-memory storage with regular snapshots for data resiliency.
- Redis offers the possibility to act as a cache with limited but strong eviction set policies. LRU is the most common one.
- The pub/sub feature of Redis is an interesting alternative for efficient and fast data distribution when we don't need a central broker such as JMS. Obviously, it requires some analysis before choosing between the bunch of providers (JMS, Kafka, MQTT, AMQP, Redis, etc)
- Redis is sponsored by Redislab which limit its functionalities. This is normal but they should push for a graphical tool for Redis monitoring. This tool is available for the enterprise edition, it would be nice to have a core version for the community
- I don't know if Redis is available in containers, this might be interesting to have such capability
71.42857142857143%
7.1
- Redis has a fast learning curve for developers and operations teams.
- Community edition allows touching a small part of Redis capabilities. In case we need support and additional features, we can decide to buy the enterprise edition which offers many additional features.
- Hazelcast, memcached and TIBCO ActiveSpaces
Memcached didn't offer the possibility to distribute data easily across nodes. Memcached was more for near cache features whereas we were looking for a distributed cache.
Hazelcast and ActiveSpaces are considered as data grid with a powerful approach while distributing data (i.e. geo localization of data) but were more complex in terms of administration compared to Redis.
Hazelcast and ActiveSpaces are considered as data grid with a powerful approach while distributing data (i.e. geo localization of data) but were more complex in terms of administration compared to Redis.
15
Redis was used by many teams in my previous company. The main usage of Redis across these teams was to cache web sessions. Redis was also used in various PoC for exploring distributed cache and how efficient Redis was/is compared to the ad-hoc implementation of Memcached.
Majority of teams were working on internal projects and were not focus on client delivery.
Majority of teams were working on internal projects and were not focus on client delivery.
5
Colleagues supporting Redis (i.e. responsible) are mostly data and system experts already working with data distribution (NoSQL databases). They have a strong understanding of the system and network constraints (such as geolocalisation, bandwidth control, data sharing, etc).
They also have a clear understanding of alternatives and why, for specific use cases, it is better to use in-memory database compare to physical storage.
They also have a clear understanding of alternatives and why, for specific use cases, it is better to use in-memory database compare to physical storage.
- The main use case was for caching data in a distributed context. Redis is really powerful while dealing with data sharding and heavy traffic load
- Another use case of Redis was the capacity to server faster data compare to physical databases. It was used for non-critical systems.
- The last use case (minor) was to explore the pub/sub capability of Redis in the context of the multi-tenant application
- To be honest, we were not really innovating with Redis, we were using common features.
- I'm not anymore working for the company, but I remember that LUA script was explored. They were also trying to build bigger cluster (~100/150 nodes)