Overview
What is Redis™*?
Redis is an open source in-memory data structure server and NoSQL database.
TrustRadius Insights
Best open-source caching database
Set up & forget
Redis is THE solution to all your caching problems
Great in-memory database solution
Redis is a great product offering from Amazon
REDIS great as K/V cache
Redis Review
Redis Solves many application caching problems.
Fast and reliable
Best DB for a gaming company willing to scale overnight
Redis is awesome!
Redis will improve reliability and performance and reduced costs.
Improve performance at a reduced cost
Gets the job done!
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
Entry-level set up fee?
- Setup fee optional
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Features
NoSQL Databases
NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.
- 10Performance(69) Ratings
How fast the database performs under data load
- 9Availability(69) Ratings
Availability is the probability that the NoSQL database will be available to preform its function when called upon.
- 9Concurrency(68) Ratings
Concurrency is the ability for multiple processes to access or change shared data simultaneously. The greater the number of concurrent user processes that can execute without blocking each other, the greater the concurrency of the database system.
- 8Security(63) Ratings
Security features include authentication against external security mechanisms liker LDAP, Windows Active Directory, and authorization or privilege management. Some NoSQL databases also support encryption.
- 9.4Scalability(69) Ratings
NoSQL databases are inherently more stable than relational databases and have built-in support for replication and partitioning of data to support scalability.
- 9.9Data model flexibility(62) Ratings
NoSQL databases do not rely on rely on tables, columns, rows, or schemas to organize and retrieve data, but use use more flexible data models to accommodate the large volume and variety of data being generated by modern applications.
- 9.3Deployment model flexibility(62) Ratings
Can be deployed on-premise or in the cloud.
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
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
Comparisons
Compare with
Reviews and Ratings
(224)Community Insights
- 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
(51-75 of 75)Redis makes your application super fast.
- 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
Redis is fast and just works!
- PubSub notifications: easy to use and just works.
- Redis has a lot of different data structures and it's easy to find the best one for any problem.
- Simple lightweight protocol.
- It just works and works fast!
- Single threaded nature of Redis can hurt if you not following best practices. For example, small values, don't use heavy blocking commands.
- Expiration can be set only on a key level, and cannot be set for a hash item.
Performant In-Memory Database
- 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.
- Automatic failover
- Exhaustive set of data structures
- If you want some simple messaging service, Redis pub/sub is excellent.
- It's difficult to understand the use cases initially. The website should talk about "why Redis" first, then "how".
Redis is the DB you didn't know you need.
- 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.
Redis is a nice transition to take
- Basic Storage
- Caching
- Queues
- Scripting is sometimes cumbersome
Our experience with Redis Enterprise
- 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.
Redis on high scalability world
- Session Management
- Key value pair DB structure
- High scalability
- Flash instances
- Failover Replicas
- Data Consistency
Redis: More than just cache
- Simple Key Value storage
- Easy interface compared to other databases
- Reliable performance characteristics
- Redis needs better distributed support. I know this is not the point, but a distributed Redis with some CAP tradeoffs would be useful
- Redis should be more clear on its pooling capabilities. Should you use a pool or just use a single connection?
- It would be nice if Redis had a better CLI
Redis Labs is great!
- Fast.
- Reliable.
- Regarding Redis Labs, the UI is not intuitive.
- Redis Labs needs an API so I can automate tasks programmatically.
Redis Review
- Response time - the time taken to store or retrieve something from Redis is minuscule compared to most of the alternatives that we are aware of.
- Value for the money - every time we offload data storage to Redis it saves us money, compared to using something like MongoDB or AWS.
- Better documentation.
Easy enterprise caching with Redis
- It's an incredibly fast database with restrictions. It only has key-value combinations but good anyway.
- For caching, at the first request-> write to the cache and read from it since DB query is expensive.
- Persistence, It's like having your session active any time you want.
- Software-based so the high availability configuration is a little bit tricky.
- The expire function is manually managed, so keep all your variables well documented.
- Better to create a Proxy service to deal with Redis values in order to isolate your app from the complexity (not too much anyway).
Redis: Simple and Fast
- Simplicity combined with power. The Redis API is very simple to use, but it also excels at handling large amounts of traffic.
- Redis is scalable and can seamlessly scale outwards to store and retrieve larger amounts of data.
- Redis has an incredibly strong community and tool suite. There is an ample amount of tutorials and connections, making it a great choice regardless of your tech stack.
- It would be better if there were some more advanced tooling. It doesn't feel quite as robust as some data storage options.
- It's unclear how much the core team is doing to advance the product. I'm not a hardcore follower, and there is little news about what is happening.
- Sometimes things can feel a little too abstracted. I've used it for a long time, but rarely know what is happening underneath the hood.
Redis is a hammer in search of a nail.
- 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.
Dead-Simple Configuration and Scary-Fast Performance
- Key/Value datastore. Redis is incredibly fast when it comes to simple "phone book-style" lookups.
- Queue orchestration and management when there are many nodes in a system that need to all be on the same page.
- Dead-simple installation process. It takes about 3 minutes to install Redis and get the service started.
- I am unable to come up with any legitimate cons, but one thing to note is that Redis, by default, will be installed with no password, leaving it open to the world if the host is not locked-down with a firewall.
Redis Review
- Very, very fast due to the in-memory data store, which makes it highly scalable on rational-sized hardware.
- Fills a number of different use cases: can build message broadcast, task queues, sorted sets (i.e. leaderboards), and database caching all with the same tool.
- A robust third-party ecosystem of deployment options (like AWS) and libraries in a number of common programming languages.
- Can be difficult to set up as it scales past a single write node.
- While Redis can preserve state by writing to the file system in a couple of ways, it can still be cumbersome to standup a cluster with history.
We love Redis
- Cacheing APIs - this is where it shines for us
- Quick in memory database of key value pairs
- The tooling around Redis provides insight into what you are caching and provides easy methods to clear some caches and not all
- New versions of the tooling are not easy to install compared to previous generations
- Redis is easy to install and maintain.
- Redis is very fast, especially with set operations.
- Redis is cost effective.
- Clustering, especially with multiple write nodes, can be difficult to configure.
- Configuring extremely high availability can be difficult.
Redis is goooood!!!
- 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.
Redis - memory is the new disk
- 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
Trust Redis: A Review on TrustRadius
- In memory caching
- Fast read and write access
- Data structure based API
- Clustering and sharding
- Self managing for high availability
- Failover
A good key-value\no SQL product
- key - value logic
- no SQL structure
- really speedy queries
- need an initial implementation
- without a correct key - value queries do not perform
- need a change of the actual application to move from SQL to Redis
- 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)
Redis is great, and your application can be great too!
- Caching - that's what it's built to do, and it does it well.
- Performance - pretty much everything happens in memory, so it's blazing fast.
- Atomic operations - when you need a distributed counter, Redis is a great option for avoiding race conditions across services/servers.
- Blocking calls - polling for changes kinda stinks, and Redis gives you the option to perform blocking calls that immediately return when data is ready.
- Complex querying - Redis is not a relational database, and should not be used as one.
- Clustering - this is always a complicated topic, but it could be made more simple.
Redis: A Caching Database on Steroids
- Quick lookup/interaction with data
- Excellent key-value storage where everything is treated as a hashtable
- Cheap alternative to other storage solutions
- Mass amounts of storage is supported
- The backup and recovery solutions are not ideal; recommend backing it with a more durable option
- The spin up to find an optimal setup for performance takes time and testing
- No super user friendly GUI application to interact with the data