TrustRadius
Redis is an open source in-memory data structure server and NoSQL database.https://media.trustradius.com/product-logos/N7/OG/GE6NPTP63INR.PNGRedis, a fast, reliable and well supported data storage systemWe'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.,9,Existing tools like Redisson that were built over Redis reduced dev time in solving challenging problems, which had a positive impact on ROI. We initially misused Redis for persistent storage which had a negative impact on ROI because we were paying a lot for inactive users. The increased performance we achieved using Redis in areas like locking helped us improve the performance of our system reducing the likelihood of system timeouts.,Our greatest gains in using Redis have come in the area of improved system performance. It boosted performance on requests by up to 5x over solutions built on our core database. We've also improved system reliability using Redis features like expiry, which has helped us mitigate risks associated with data corruption when system errors occur.,Yes,Product Features Product Usability Product Reputation,We've found our greatest development architecture benefits in using Redis have come from the many tools available for those using Redis. It is supported by multiple languages and libraries. We started with Jedis and later moved to Redisson for internal development, we've also found a number of tools like distributed caching offer the option of being seamlessly built over Redis.,,MongoDB, AWS OpsWorks, Google Cloud Pub/Sub, GitHubRedis is AwesomeRedis 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.,10,Reduced load to the primary transactional database. Ability to launch open source-based solutions backed by Redis quickly to reduce "not invented here" within engineering. Reduced infrastructure gave Redis' small footprint and flexibility for temporary caching as well as permanent storage.,Our organization has been able to use a single solution instead of multiple to handle caching, NoSQL data storage, and pub/sub. This allows for flexibility in options for engineers with simplified management for operations. Using hosted providers such as RedisLabs or AWS allows minimal involvement or overhead in production. The number of open source solutions already using Redis is high as well, this allows us to reuse the same infrastructure for out-of-the-box solutions.,No,Price Product Features Product Usability Product Reputation Prior Experience with the Product,The simplified list of commands to get/set keys and manage your keys is listed on a single page. Many languages have plugin adapters and libraries that allow for native and natural use of Redis as a data store without having to memorize the list. When looking at the CAP theorem, the approach Redis has is really simple for engineers to understand even if they know little about NoSQL or key-based storage.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.,9,Redis can help you save money optimizing your code since it's super fast and won't slow you down. Redis on Flash can use SSD disks to provide you with more storage without the need of having everything in RAM.,Redis has helped us a lot. We started using it when MySQL wasn't fast enough for our needs, and we have never stopped since. With latencies of less than a millisecond and sometimes close to a microsecond, it's the fastest there is. Since it can be clustered, sharded and replicated with very simple steps, it's really reliable which is hard to do without losing speed.,Yes,Prior Experience with the Product Vendor Reputation Third-party Reviews,Amazon ElastiCache,Docker, Kubernetes, Nomad, AnsibleIf you need lots of user sessions, this is the product to useRedis 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,9,We can scale as needed (like for the Super Bowl) and not go down.,We can stream several million hours of live TV from 210 DMAs and service all those viewers and it just works.,No,Product Features Product UsabilityGet a cache server on steroids with Redis and get rid of those Memcached instancesWe 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.,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.,9,Implementing Redis for the first time in a project was super easy and it didn't add any noticeable cost to development or release processes. Replacing Memcached use cases with Redis was also almost entirely transparent during implementation. Having a high-performance/high-availability software solution for free and open source is a great option in this market.,Being able to deploy different instances of Redis to cover caching, messaging, sub/pub, syncs, and temp storage is helpful as we don't need expertise in many different solutions for all these cases. By just deploying Redis and tweaking each instance for their use case, we get more value from our initial investment (which is only on manpower, because Redis is Free and Open Source), and we can focus more on our business and less on infrastructure/implementation details.,Yes,Price Product Features Product Usability Product Reputation Prior Experience with the Product Third-party Reviews,We've deployed Redis into a Kubernetes cluster by just using their Docker images. Deploying this way saves a good amount of time, given that you just need to write the Pod configuration and mount the pre-built Docker image. After that, it's just a matter of deploying your Kubernetes environment and you're good to go. From there, using an SDK for your programming language is mostly transparent for any developer, and then you have your application integrated with Redis in no time.,MongoDB and Google Cloud Pub/Sub,Google Cloud SQL, Google Cloud Storage, PostgreSQL, MySQLRedis RocksWe 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,10,Redis is widely applicable, so knowledge of it transfers between use-cases Its widely used, so there are cache backends for common frameworks, like Django in our case,As an in-memory database, it is very fast, and useful for a wide range of data needs, including caching. The variety of data types provided are capable of transforming it from a simple key-value store to one that is powerful enough to run fairly advanced applications while keeping that awesome speed advantage.,No,Price Product Features Product Reputation,We have relied on Redis in our application since the beginning, so it's difficult to compare what it would have been like without it. However, we find that Redis is a consistently stable and simple data store that gives us the features we need to communicate between processes effectively and efficiently. This enables us to build on top of this code, as we know that we can trust it.,PostgreSQL, RabbitMQRedis : Effective cache management solutionFirst, 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.,10,The positive impact is increased availability of contents on a slow network due to effective cache management & service. Another positive impact is it saving us a round trip to the server. Redis has increased the performance of the application.,Currently, Redis is in an experimental phase in my organization. As I already mentioned that it's yet to be deployed in a production environment. We will study its impact when Redis will get involved in the real transaction process. So, far we have calculated that we can fetch some latency issues but, we are yet to establish it.,No,Product Usability Prior Experience with the Product Analyst Reports Third-party Reviews,Yes, we are surely being benefited by Redis features. Redis is a easy to use and maintain software. I have personally been able to manage & develop various cache & message broker related solutions easily. Production-grade deployment is also easy because I have tested it in semi prod environments, which is almost like our prod.,Oracle Database 12c, Eclipse, Oracle Java SESuper fast and easy to integrateWe 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.,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.,9,We use Redis for the purposes of routing data within our infrastructure. In this use case, we want there to be a little additional latency as possible. In this, Redis does a great job.,We primarily use the traditional Redis simple key-value pairs. Speed and stability are what we rely on Redis for. In this aspect, we have seen exceptional performance and uptime in all the applications we use Redis in.,No,Price Product Reputation,While we don't really have much to compare with since we chose Redis off the bat for the purpose we're using it for, I can say that implementing it in our application was quite seamless.,Amazon ElastiCache,MongoDB Atlas, Node, StripePerfect for caching and expiring data storageWe 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.,9,It allows to speed up several internal tools.,We use Redis as a caching layer for almost all internal tools. For some tools, Redis is not only used as a cache, but it takes care to filter out duplicated jobs that would otherwise waste precious computational resources.,No,Product Features Product Usability Product Reputation,Redis is central to one of our internal tools to provide caching, rate limits and duplicate removals. It makes the tool much faster easier to manage.,PostgreSQL, Google BigQuery, PrometheusRedis ReviewWe 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.,8,Huge savings on loading time in applications. Additional cost in hosting Redis servers in AWS.,It has enabled us to easily cache lots of data. We are able to use Redis per our wish, without much thinking.,No,Price Product Features Product Usability Product Reputation,Yes, the interface is very simple to use and we are critically depending on it.,,IntelliJ IDEA, Slack, JIRA SoftwareRedis 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,5Things you can do with RedisRedis 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,10,Reduce processing and analytics time Improved concurrency of data Streaming data in real-time.,Redis on a basic level has impacted our organization positively by cutting down the time previously consumed to process data directly from the database by more than half the time. It has also benefited us in terms of real-time analytics and live data updates during the streaming of data.,Not Sure,Price Product Usability Product Reputation Positive Sales Experience with the Vendor Third-party Reviews,Faster execution time was a factor we highly considered while choosing Redis we did not want to waste time on a product that cost us time for less. Redis helped us cut the time by more than half and provided an efficient and excellent performance to our architecture. It also helped us eliminate the complexity of the previous existing architectures.Redis is the best cache database on the marketWe 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.,10,Server performance improved by 70%. The cost of the tool is recovered in the profit generated in 3 days of operation.,Previously, transactional applications were very slow. Today the performance has improved to 60%. Redis is very stable and a cluster with three servers was installed to have high availability and adding new servers is simple so it is easy to scale.,No,Price Product Features Product Usability Product Reputation Existing Relationship with the Vendor Positive Sales Experience with the Vendor,Redis Cloud,Microsoft SQL Server, .NET, JIRA Software, Jira Service Desk, RabbitMQ, Azure DevOps (formerly VSTS), OpsNowRedis: 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.,10,Increased server throughput. Faster & better user experience.,We use it for caching and being in-memory, it's quite fast. Since we also use it for background processing store, its high-speed access, stability gives our pipeline the consistency that it needs to process millions of jobs daily.,No,Product Features Product Usability Product Reputation Vendor Reputation,Redis has been designed to simplify app development by providing a development architecture that results in cleaner code, faster execution time, better application performance and network utilization.,MongoDB, PostgreSQL, Amazon DynamoDBReduced costsOur 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.,9,Having to train users on it takes some time. Cost savings and infrastructure. It's increased our server capacity.,It has help speed up our CRM platform.,Yes,Price Product Features Product Usability Product Reputation Prior Experience with the Product Analyst Reports Third-party Reviews,It has streamlined our application development, and cut infrastructure costs.,,Microsoft Azure Machine Learning Workbench, DynamicOps Cloud Suite, Microsoft Dynamics 365 (formerly Microsoft Dynamics CRM)WowRedis 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,9,Positive: application development, can now lock Positive: can queue,Works great,No,Price Product Features Product Usability Product ReputationFan Redis userWe 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.,10,Prevent huge database cost with Redis as cache, Prevent huge server cost with Redis as a transport layer to other servers.,No,Price Product Features Product Usability Product Reputation Vendor Reputation,We can have a separation of concerns in our code thanks to Redis as a transport layer.,,Firebase, Google Cloud DatastoreCache in actionWe 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,9,We were able to deliver solutions faster and it was easy to get going for developers.,In certain use cases in a big way. We were able to achieve seconds latency to milliseconds latency.,Yes,Price Product Features Product Usability Product Reputation Analyst Reports Third-party Reviews,Yes, we were able to achieve milliseconds response for many critical calls with the above-supported features.,,Amazon DynamoDB, PostgreSQL, MemSQLRedis will improve reliability and performance and reduced costs.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,9,Redis has reduced our licensing costs by around 15% compared to running SQL exclusively Performance has increased Reliability has improved greatly compared to when we ran everything on SQL,Our EMR\Billing platform has been able to increase performance by about 25%. We have been able to provide customers with more data and a shorter time. We are now able to attract more enterprise sized customers than before since we can support the data they provide to us and are able to process it quickly.,Yes,Price Product Features Product Usability Product Reputation Prior Experience with the Product Third-party Reviews,Our code structure has greatly improved and as a result performance has increased. Since our code is cleaner our DevOPS engineers are better able to under stand our code and our DevOPS on-boarding time has been reduced. Reliability has also improved since we are able to process more data requests.,Oracle Analytics Cloud,Amazon Elastic Compute Cloud (EC2), Amazon DynamoDB, Amazon S3 (Simple Storage Service)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,9,With Redis we can serve web pages must faster. Faster pages means better business. Scaling across many servers we're able to support millions of visitors a month.,The ability for Redis to go really fast using in-memory storage has given us the ability to serve cached web pages blazingly fast. Beyond caching, we have been able to span across multiple servers to handle loads of millions of visitors to our websites. Although we only use it on one platform, the ability for it to be used across platforms is attractive.,Yes,Price Product Features Product Reputation,We raved all the time about the application speed due to the performance gains we got initially from Redis. While we still actively use Redis, it's not something that often gets discussed. That's a good thing. It's rock-solid stability and performance has given us an advantage in website building and development.,MongoDB, CouchDB, PostgreSQL and MySQL,MySQL, PostgreSQLImprove performance at a reduced costWe 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,10,The ROI on Redis has been great. We were able to cut our infrastructure costs by 25%. Scalability is one of the key benefits of Redis. Increased performance at a lower cost is a huge benefit.,We have been able to increase performance and also been able to reduce infrastructure costs. We use Redis in our EMR messaging platform and have been able to provide clients archive history search queries of messages much faster.,Yes,Price Product Features Product Usability Product Reputation Prior Experience with the Product Vendor Reputation Third-party Reviews,We have been able to improve our application performance and code structure as a result of migrating to Redis. Also, reliability has improved greatly. Scalability is easy and improved performance for our larger customers.,Microsoft SQL Server,Microsoft Office 365, Microsoft Azure, Amazon S3 (Simple Storage Service)The 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 ReviewRedis 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.,9,Redis improves the UX of our app by allowing us to show real-time geolocations instantly on user connections. Given that our app is a massive carpooling app, improving our UX allows us to be seen as more reliable and stable. A faster server response to our app. The built-in geolocation capabilities have saved us a lot of time on having to develop that logic into another database.,Redis high-speed database has allowed us to deliver a better user experience by letting us show last known locations instantly. The multi-platform support has been useful too because it has allowed us to implement it seamlessly across our platforms.,No,Price Product Features Product Usability Product Reputation,Faster execution time and app performance is the main feature that we look for when using Redis. Our organization has benefited from decrease response times and low overhead on requesting last known locations, allowing us to have a faster interface and better information for our users.,MongoDB, MongoDB Atlas, AWS Elastic BeanstalkEnterprise performance at a fraction of the priceWe 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.,8,We've seen less downtime with more stability. Reduced build-out costs. Faster development of new database structures.,It has greatly increased speed and reliability.,Yes,Price Product Features Product Usability Positive Sales Experience with the Vendor Analyst Reports Third-party Reviews,Yes, it has streamlined our development cycle and decreased performance issues.,Microsoft Azure,Amazon DynamoDB, Amazon Elastic Compute Cloud (EC2), Azure Active DirectorySimple yet powerful datastoreWe 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.,10,Caching done in redid gives good performance gains, almost like a memory store.,It has been reliable especially for our main use case as a queue backend (using Resque). It's really fast and stable.,No,Price Product Features Product Usability Product Reputation Prior Experience with the Product,Yes, instead of worrying about memory management, we use Redis for quick storage and retrieval, and persistence across server restarts (we use Heroku, so there isn't persistent storage built-in).Windows, Linux, Mac
Redis
170 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>TRScore

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
170 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?

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-25 of 70)

Companies can't remove reviews or game the system. Here's why.
Eric Mason profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is a great tool for distributed caching and synchronization/locking in systems with multiple instances. It also works well for non-persistent data that doesn't grow over time, for instance, you might want to use Redis to manage a queue. It's a particularly good choice for pieces of data that are frequently updated.

Conversely, due to price/data I wouldn't recommend Redis for persisted or infrequently accessed data.
Read Eric Mason's full review
David Sommers profile photo
September 21, 2019

Redis is Awesome

Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is great for queues (push/pop) and pub/sub. It can also be used for caching though take care of managing those expire settings and don't mix permanent keys with expired keys on the same hosts unless you want to spend some time troubleshooting unplanned evictions. When looking at open source solutions to messaging, queuing, background jobs, etc. - you'll find many solutions work with Redis out-of-the-box.
Read David Sommers's full review
Emiliano Perez profile photo
October 08, 2019

Gets the job done!

Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is fast, super simple and reliable. You need minimum security measures like having your data replicated and (at least daily) backups for emergencies. If you want to have all this done automatically by a simple UI, then Redis Enterprise is a must We have been working with Redis for over 5 years and we couldn't be happier.
Read Emiliano Perez's full review
Jeanette Kreutner profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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
It is well suited where you need lots of calls to a database, not the best solution for long term storage
Read Jeanette Kreutner's full review
Leonel Quinteros profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
  • 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.
Redis is great for any cache service with data persistence implementation. If you need a super-fast cache, you can always use the in-memory cache (without persistence) to improve performance and still get all the benefits of the service.
It's usually compared to Memcached, and in terms of performance I think they're very similar, and for some critical applications, Memcached may be a better option. But the feature-rich characteristics of Redis will position it in a more competitive place against many applications.
Read Leonel Quinteros's full review
Ryan Hiebert profile photo
September 14, 2019

Redis Rocks

Score 10 out of 10
Vetted Review
Verified User
Review Source
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
Redis is well suited for caching, as well as distributed coordination between workers. It doesn't work extremely well for cases where the data is highly interconnected, though RedisGraph may be a good solution to that (I'm not able to review it, because I haven't used it). Its variety of data types makes it possible to do some rather advanced things easily, and when combined with scripting, there are very few hard limitations on what is possible.
Read Ryan Hiebert's full review
Manjeet Kumar profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Well suited scenarios: Cache management, real-time analysis of events, and leaderboards/counting. Less appropriate scenarios: Persistence and clustering.
Read Manjeet Kumar's full review
Anush Ramani profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
  • 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.
I would highly recommend Redis as a hosted solution. We tried self-hosting initially but gave up on that due to the overhead of maintenance. We really want to use Redis in mission-critical projects and as such, reliability is paramount. Self-hosting leads to concerns with reliability—that's best left to services for whom that is their bread and butter.
Read Anush Ramani's full review
Davide Pedranz profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Well suited:
  1. Cache
  2. Filtering out duplicates
  3. Implement rate limits
  4. Store access tokens or revoked credentials
Not suited for:
  1. Storing complex data (go for a traditional database instead)
Read Davide Pedranz's full review
Shehan Wickramarathne profile photo
June 25, 2019

Redis Review

Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is well suited for quick caching and performance-centric applications.
Read Shehan Wickramarathne's full review
Gunasekar Duraisamy profile photo
June 17, 2019

Redis and its CSAT

Score 9 out of 10
Vetted Review
Verified User
Review Source
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
It is well is suited as an in-memory key value store for applications which require very little response time. The data can be stored and retrieved from Redis in minimal time when compared to traditional databases. It is not suitable when the data cannot be stored in memory completely.
Read Gunasekar Duraisamy's full review
Joseph Ngugi Muiruri profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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
Using Redis to cache our most frequently accessed data was one of the best decisions we ever made.
When it comes to performing analytics, Redis is very efficient at that as well as handling large amounts of data common in the data analytics industry. Redis also acts as a very excellent NoSQL database.
Read Joseph Ngugi Muiruri's full review
Eduin Zuloaga profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
The best scenario for Redis is where fast response speed is required to have an optimal performance of the applications, or when it is required to have data that is consulted on a recurring basis.
Read Eduin Zuloaga's full review
Kiran Narasareddy profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Well suited for a real-time stock price ticker. Not well suited for eCommerce search.
Read Kiran Narasareddy's full review
Matthew Kuc profile photo
August 27, 2019

Reduced costs

Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is suited to database and back-end data processing.
Read Matthew Kuc's full review
Evan Sarmiento profile photo
August 24, 2019

Wow

Score 9 out of 10
Vetted Review
Verified User
Review Source
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
For queueing, locking, and caching.
Read Evan Sarmiento's full review
Florent CLAPIÉ profile photo
August 23, 2019

Fan Redis user

Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Perfect for caching the database and as a transport layer.
Read Florent CLAPIÉ's full review
Ajmal karuthakantakath profile photo
August 12, 2019

Cache in action

Score 9 out of 10
Vetted Review
Verified User
Review Source
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
HTTP sessions, caching, and as DB for a decent size data.
Read Ajmal karuthakantakath's full review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
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
Redis is great at at reducing your reliance on SQL and the cost associated with running a SQL infrastructure.We have been able to scale out and improve performance on database requests. Reliability has also great improved over running a SQL infrastructure.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
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
Redis is well suited for front end caching of websites and apps. We also use it successfully to manage our web/app cookies and sessions. Everything in Redis is in your RAM, so if you need anything stored permanently you'll need to turn on the persistence options, which will slow down Redis a bunch since it has to write to disk.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
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
Redis is great for any organization that requires data-intensive tasks that quire records or require large sets of data. Redis has greatly improved our messaging EMR performance at reduced costs compared to if we built our own solutions. If you require fast response speeds then Redis is your provider. Great for back end data base processing.
Read this authenticated review
No photo available
September 11, 2019

The Redis Imperative

Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
Well suited for keeping track of scoring scenarios.

Poorly suited for long term storage of data.
Read this authenticated review
No photo available
September 06, 2019

Redis Review

Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Redis is very useful for real-time scenarios where disposable recent information may be useful such as a location share app, mobile games or even a volatile chat. I must say, I haven't looked into Redis beyond these examples, so I couldn't recommend it for other use cases. The obvious less appropriate use would be for something such as a full database stack.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Reseller
Review Source
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.
Redis is great to eliminate on-prem infrastructure. It's less appropriate for international data security compliance protocols.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Good for a fast datastore if need something apart from memory. Not great if you have complex querying needs since it's a key-value store.
Read this authenticated review

Feature Scorecard Summary

Performance (62)
9.3
Availability (62)
8.8
Concurrency (61)
8.8
Security (57)
6.6
Scalability (62)
8.6
Data model flexibility (55)
7.7
Deployment model flexibility (55)
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