TrustRadius
Redis is an open source in-memory data structure server and NoSQL database.https://media.trustradius.com/product-logos/N7/OG/GE6NPTP63INR.PNGRedis and its CSATWe 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,9,The productivity increased Needs more security aspects Performance has improved tremendously,After using the Redis in my implementation the performance has increased over 90 percent. This is only because of Redis. I compared Redis with other similar technologies but Redis stood out in reading performance. I selected Redis for my implementation. Redis performed as expected and I got a good name in my company.,No,Price Product Features Product Reputation Third-party Reviews,Developing applications with Redis is never a difficult task in our organization.,CodeIgniter,CodeIgniter,1,,in-memory cache, where we store our data it can be very helpful in key management also storing the batch data,5Redis on high scalability worldWe 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.,Session Management Key value pair DB structure High scalability Flash instances,Failover Replicas Data Consistency,10,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.,Cassandra, MongoDB and Aerospike Database,Google Cloud SQL,75,100,10,key value streams hash,nothing,No,10The Redis ImperativeRedis 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.,8,Redis has helped to save time by reducing our usage of data access methods on our server.,Redis allows our client architecture to respond quickly for requests that are not required for traditional database methods. It also serves as an intermediary between mobile and client architecture.,No,Price Product Usability Product Reputation,Our organization has benefited by using Redis as in intermediary to replace Firebase for database propagation methods and distributing message notification between clients.,,Alchemy Catalyst, Apache Kafka,3,1,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.,9,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.,8,No,5,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,7Redis 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.,10,Redis has small learning curve. Just a couple of small Linux type commands, and that's pretty much it. For this reason, everyone was on-boarded to use Redis almost within a week. Since Redis has good language support, we were comfortable using Redis for Java as well as NodeJs. Redis is overall fast. When we compare Redis with an actual database, Redis wins just because of how fast and easy it is.,Amazon ElastiCache,ServiceNow, JIRA Software,10Redis - memory is the new diskI 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 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,8,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,Vagrant, Docker, OpenShift,9,15,5,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)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.,Easy to setup, and configure. Would like a larger community to contribute to it. Pretty reliable, never had malformed data on slaves. Can have multiple instances running on the same box which is good. Data sharding though it not as great as I'd hoped it to be. Also, API calls to monitor isn't that bad but would like [more] monitoring (in depth) than is provided.,8,Reduced need for high end DBservers. Better than memcacheD. Doesn't do well for time series data though, which sucks.,Aerospike Database, MemCacheD and Couchbase,Aerospike Database, Couchbase Server, MemSQL,8Trust Redis: A Review on TrustRadiusRedis was used internally by software development teams as part of a web application stack. Each development team was free to use alternate technologies, including none at all, but for teams with performance requirements, Redis was chosen to provide an in memory cache layer buffering web requests from directly hitting the database.,In memory caching Fast read and write access Data structure based API,Clustering and sharding Self managing for high availability Failover,Redis' in memory implementation makes it particularly well suited as an application cache. For Web tier stacks, it can be used for session management. In addition to its in memory implementation, its core API is based around data structures, not just Key-Value Pairs, making it far more versatile for caching database responses.,9,Redis has reduced the hardware requirement cost for our RDMS machines, by offloading work to redis servers There is increased complexity which translates to development time, in order to build an application to leverage Redis The increased complexity in application design has a net benefit of increasing fault tolerance,Memcached and MongoDB,Evernote, G Suite, Stripe,9A good key-value\no SQL productWe have tried using Redis to move from a relational DB to a key-value logic. In view of the use of a DB not SQL, it is certainly performant even if unlike other SQLs, it requires a little more reasoning about the proper analysis of the key value to be used and the way in which they are then interrogated.,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,Redis is definitely a good solution (in the best case) if you are willing to change your SQL structure to a no-SQL structure, but only if you know what you want to get and what kind of application you want to access the data, otherwise the performance can be very degraded.,8,SQL server freed from workload less effort to clean up unnecessary data,MongoDB,8Redis: Awesome in-memory key-value distributed CAP compliant storeWe use Redis for low latency repetitive point queries. To break it down: Low latency: As it is in memory, saves on I/ORepetitive: 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 againPoint 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),Redis ModulesAbility to extend Redis is a huge power using its robust backend pipelineRedis Enterprise has smart support for FlashRedis (e) smartly decides, based on usage, which keys to put in RAM and what to put in SSD, opening up whole new possibilities of storing more data and not needing to create subsets for RedisOptimistic concurrency control support An educated developer knows better on what objects to obtain lock and avoid concurrency and dead lock problems which other databases run into. Redis gives the flexibility to either create a critical section or obtain optimistic locks on certain variables,10,We use it all the time for point queries and it worked well Though it is in-memory it is distributed and durable We need high availability for ETL and low read latency accelerates even further,MemSQL,React,10Redis: A Caching Database on SteroidsWe use redis as a cheap, available, quick storage option. Think of it as a cache on steroids. It lets us store mass amounts of data and access it quickly. The best part is the access cost is not per demand, you are just paying what is hosting the redis clusters.,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,The best part of redis has been the the millisecond response times for CRUD operations to data, the only caveat is you might have to change how you store the data since everything is key-value with query lookup schema. Sets are supported, but the idea of scan/get all are not really supported, but that functionality can be coded. We used methods such as one key holding entire table of data or having a key that holds a set of all hash keys in a table.,9,One implementation of Redis saved our company thousands of dollars a month in data storage by switch to redis We were able to increase our performance and scale the system to millions of users without drastically increasing costs We had to accept possible loss of data during a backup/recovery situation, so data was not critical,Amazon DynamoDB, Amazon S3 (Simple Storage Service) and Microsoft SQL Server,Amazon DynamoDB, Amazon S3 (Simple Storage Service), Amazon Redshift,10Redis is great, and your application can be great too!We mostly use Redis as a cache for data flowing through a data processing pipeline. When we have surges of activity, we rely on redis to alleviate the stress on our pipeline and ensure that no messages are lost. We also use some of the features in Redis to synchronize our services across several servers.,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.,10,Redis is free, so the ROI is pretty incredible. Setting up redis is as simple as installing a package, launching a service, then configuring your application to talk to it. Very low overhead that way, and very quick and easy to get up and running.,memcached,PostgreSQL, Elasticsearch, Gitlab,10gets your job done fast, smooth and fast.We have a range of sensors that transmit data to our server and this data is stored in a mongodb database; while it's stored we needed a way to transmit the data to our web application to generate live charts on the fly; to accomplish this we used redis coupled with socket.io since the application storing the data and the application generating the charts are seperate entities. Though there are other ways to accomplish this, redis has been really useful is helping us accomplish this. Another place where we are using redis is for our caching, since we deal with high volumes of data, we use redis as a caching mechanism and it has done wonders for us.,Speed. The very fact that it is used for caching systems should verify that it must be really fast. Pubsub. Though there might be alternatives that solve this problem as well, in our case redis did it accurately and without any data loss. Redis has a couple of data types that aren't available in other systems. The most useful one according to me is lists; I haven't been able to take full advantage of this feature yet though.,Redis may not be for you if you want to deploy a cluster but don't have at least 5 different devices since it requires at least 3 masters and 2 slaves for the configuration to work. The reason redis is really fast is because it resides in your RAM hence it might be a problem when you have an application that needs a lot of RAM and it has to share that with redis. This will depend on the size of your application, users using the applications and obviously the amount of RAM you have.,I really liked the whole PubSub feature and I can see a lot of other use cases that it can be used in. The whole idea about a minimum set of devices to achieve clustering seems like an overkill.,10,It was worth it. Got the job done fast and accurately. No complaints whatsoever. I don't plan to explore other alternatives anytime soon.,CouchDB,Laravel PHP Framework, Trello, MongoDB,10,1,Caching database queries that are used very often and require a lot of resources. Sharing data between two applications in realtime.,Caching and PubSub were the two things I needed and Redis was able to handle them both pretty well,Didn't really find it difficult to implement the features that I was using but setting up clusters could be difficult because of the minimum requirements for slave and master.,No,9
Windows, Linux, Mac
Redis
168 Ratings
Score 9.1 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>

Redis Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Redis
168 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.1 out of 101

Do you work for this company?

Show Filters 
Hide Filters 
Showing 12 of 168 Redis ratings and reviews.
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-12 of 12)

Companies can't remove reviews or game the system. Here's why.
prakash ps profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

10
They have a good community to support our current needs. Their read write speed and rich set of datatypes are other major factors.
Read prakash ps's full review
Rahul Chaudhary profile photo
December 13, 2018

Redis is goooood!!!

Score 10 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

10
We will definitely continue using Redis because:

1. It is free and open source.
2. We already use it in so many applications, it will be hard for us to let go.
3. There isn't another competitive product that we know of that gives a better performance.
4. We never had any major issues with Redis, so no point turning our backs.
Read Rahul Chaudhary's full review
Hugo Romani Cortes profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

9
Redis is very easy to use and because of its open-source approach, we can convince a lot of people to start using it (even contractors). The philosophy of Redis is very interesting "small is beautiful" and drive all decisions while developing with such tool.
The memory optimization is also very important which allows fast data access while dealing with critical environments (SLA).
Read Hugo Romani Cortes's full review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

9
Redis is a great product, does what it sets out to do, and is continually improving. Barring a major security gaffe, there are no plans to move to an alternate solution.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

8
It is probable that we will renew it as we currently have a production environment that is using it so it will surely be our interest to follow the updates and to evaluate if possible a new renewal to keep the production environment up to date and avoid application problems.
Read this authenticated review
Nitin Pasumarthy profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

10
  1. For its simplicity is API and very familiar powerful data structures for any Computer Science engineer.
  2. To try out its always evolving Redis Modules space
  3. Due to its low footprint, would also like to try for embedded space
Read Nitin Pasumarthy's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

10
The benefits we've seen by implementing Redis in our applications have been tremendous. We have no reason to not keep using Redis. We will likely evaluate alternatives in the future, but not because of any shortcoming we've identified with Redis thus far. Sometimes there are better tools for certain jobs. We want to be open to new options if they meet our requirements better. So far Redis has done very well for us.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Likelihood to Renew

10
I am keen to explore redis even more as it offers a lot more that what I have used it so far for. I am more keen to explore the data types that it offers and how they can help me improve my code.
Read this authenticated review

Feature Scorecard Summary

Performance (60)
9.3
Availability (60)
8.8
Concurrency (59)
8.8
Security (55)
6.6
Scalability (60)
8.6
Data model flexibility (53)
7.7
Deployment model flexibility (53)
8.0

About 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 Features

NoSQL Databases Features
Has featurePerformance
Has featureAvailability
Has featureConcurrency
Has featureSecurity
Has featureScalability
Has featureData model flexibility
Has featureDeployment model flexibility
Additional Features
Has featureIntegrated modules
Has featureActive-Passive Geo Distribution
Has featureCluster Architecture
Has featureLinear Scaling
Has featureDurability
Has featureBackup and Disaster Recovery
Has featureReliability

Redis Screenshots

Redis Video

Redis Downloadables

Redis Integrations

Apache Spark, OpenShift, CData, Pivotal Cloud Foundry

Redis Competitors

Pricing

Has featureFree Trial Available?Yes
Has featureFree or Freemium Version Available?Yes
Has featurePremium Consulting/Integration Services Available?Yes
Entry-level set up fee?Optional

Redis Support Options

 Free VersionPaid Version
Phone
Live Chat
Email
Forum/Community
FAQ/Knowledgebase
Social Media
Video Tutorials / Webinar

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