TrustRadius
Redis is an open source in-memory data structure server and NoSQL database.https://media.trustradius.com/product-logos/N7/OG/GE6NPTP63INR.PNGGet 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, PrometheusDead-Simple Configuration and Scary-Fast PerformanceOur organization uses Redis for two main tasks at our organization. First, Redis is used as a traditional in-memory key/store warehouse for a cache system that contains over 400 million items, on average. Using Redis with modern DDR4 memory, we have seen incredible latency savings when it comes to keystore look-ups. Second, we use Redis to manage a distributed queue, such that numerous worker nodes can subscribe to tasks and complete them in an organized way.,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.,10,Redis requires very little in terms of host hardware, and we have Redis running on tiny servers (2GB of memory and 2 cores, for example). Redis has also replaced multiple traditional datastores like MySQL and PostgreSQL, especially when it comes to logging and caching.,The in-memory aspect of it obviously is the main selling-point of Redis, in that it can immediately decrease latency for any service or application. Moreover, multi-platform support makes it trivial to interact with Redis, and we have never encountered a programming language that did not have very high quality documentation for the Redis SDKs and libraries. As far as stability, we have never had Redis cause a server to "crash" or have had the Redis server "crash" itself. It is dead-simple to manage.,Yes,Price Product Features Product Reputation,App development frequently involves decentalized systems, and we use Redis to centrally manage all the tasks and queues that feed these nodes. Redis allowed us to get rid of multiple hardware hosts, as well as scale-down other hosts because of its incredibly small footprint and almost nonexistent network overhead. The only limiting factor is the amount of RAM on the host, because of course, that is where Redis stores the vast majority of the data.,CouchDB and Cassandra,Laravel PHP Framework, Slack, PhpStormRedis 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, MemSQLPerformant In-Memory DatabaseRedis is a vital part of our organization as it enables us to process a whole load of queues that our tools have to process. It provides so much value for us since most of our tools require queues to call APIs, etc. We used Redis because of its simplicity of setup and its fast performance. We loved Redis and sure you'd love it too!,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.,10,Increased server throughput Better user experience for users as they don't need to wait for the process at the web server level and could just visit the page after their requested job is completed.,Redis does its job well to be an in-memory multi-model database that really provides high speed and stability, also multi-platform support. Our tools mostly run on queues, so a fast database to store and process the queue items are a vital point of our business. We need a solution that meets our needs at high speed and stability.,No,Price Product Features Product Usability Product Reputation Prior Experience with the Product,Laravel PHP Framework, Nginx, MySQLRedis 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,10Blazing performance, excellent stability, and really nothing to dislike make Redis a must look at solutionRedis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to leverage it are continually being investigated and identified. It addresses data consistency and concurrency issues and provides amazing speed to what could be slower operations if handled without it.,Cache speed Support for high volume of transactions with elegant handling of data sets Ease of use - well structured and easy to implement,Price per shard is a bit high but over all there are no issues worth mentioning I've heard some wishing it supported complex queries but this is asking the solution to support operations it wasn't intended for,10,Reductions in latency allow operations that would be longer running (multiple seconds) to be performed nearly instantaneously providing for high performance. Redis allows for easier application scaling and support for a higher volume of transactions without typical performance curve limitations. Savings related to not having to pre-process unstructured data are hard to quantify but very appreciated in the sense of savings on code complexity.,The speed of operation allows for blindingly fast execution of elements of code that would normally be longer running. Reduction of the burden on our backend DB alleviates contention and congestion concerns especially for temporal/state data that really isn't meaningful long term. Stability is absolutely ESSENTIAL in our production environment and Redis does not disappoint. Lastly, multi-platform support keeps our options open as an element of future-proofing code and implementation platforms.,No,Product Features Product Usability Product Reputation,We have experienced all the benefits in just our first implementation -- the cleaner/less complex code required to manipulate data sets, reduction of the need to burden back-end database(s) with housekeeping operations, application performance improvements and definitely speed of data manipulation which enhances and optimizes application performance.,,Red Hat Enterprise Linux (RHEL), VMware NSX, HPE OneView, Foglight for Virtualization, Hitachi Content Platform (HCP), Hitachi Network Attached Storage Platform (HNAS), Hitachi Command Suite, VMware ESXi, Microsoft Azure, Microsoft SQL Server, Hitachi Virtual Storage Platform G SeriesEasy enterprise caching with RedisWe used to have most of our web apps accessing our database backend directly, and this was very resource consuming, especially in catalogs and details. This was more critical in our e-commerce storefront. With Redis, we were able to update our webs in order to cache all the queries with resources displayed frequently. In that way, we freed our servers of a huge load. The auto-expire function lets us use the Redis cache and not have to continuously monitor it.,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).,8,Positive: we used recycled hw for Redis and it worked just perfect because we had a lot of memory there. Positive: web experience increased because dynamic content is cached. Negative: migration to the cloud is not as smooth because features, such as data persistence, can be expensive.,Considering the key-value structure, we were able to fit all object model into a string in order to use a generic way to deal with cache'ing. A middleware is required in order to deal with serializing which is good because the App remains generic and for now we can use Redis until the next alternative is available. That means we can use the middleware with no changes for any app. Because of this, this middleware is the entry point for every single DB query.,No,Analyst Reports Third-party Reviews,We compared the actual architecture with cache against the old one with no cache and the difference was more than clear. We put the Redis server in a different network segment and the response time goes up. About cleaner code, the original app is mostly the same but with no dependencies of the DB interfaces. Now we have an API that we can switch at will handling all the complexity. Of course, you have to expend some time developing this middleware but it's not a big deal. In the end, we have a cached DB - API - Apps combination that allowed us to increase concurrency with no major investment on infrastructure.,MongoDB, CouchDB and HBase,Oracle Database 12c, Microsoft Visual Studio Code, NodeRedis makes your application super fast.We are using Redis for one of our clients. We wanted to find a way to handle huge amounts of data for every user search and their MySQL was not able to handle it quickly. We were discussing going more toward NoSQL. After more R&D, we chose Redis. Now it is handling data in an excellent way. It's for a travel product where we are searching hotels and flight for queries given by users, and Redis is rocking here.,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,10,Redis require minimum hardware to setup. It is very fast to read and write data compare to other database. Now it replacing traditional data store.,We are using Redis database to improve the performance of our application. Redis plays a major role in our application. It acts as a persistence database as well as a cached database and we are using it for the distributed queuing system. It reduces our development time and database maintenance time, and requires very little maintenance time on the server.,No,Price Product Features Product Usability Product Reputation Prior Experience with the Product Third-party Reviews,Yes, Redis has a very simple and easy architecture. It is compatible with many languages. It provides speed and scalability which every software developer love to implement in their application. Currently, we are using Redis with Elixir, Nodejs and Python, and we feel Redis has a reliable network connection and concurrency among every API.,MongoDB and CouchDB,Google Cloud SQL, Elasticsearch, Google Compute EngineRedis is the DB you didn't know you need.We are starting to move towards using Redis as our primary storage for performance and simplicity reasons. We have been using it for the last 5 years as a Caching and Session storage mechanism, but last year we started to implement it across multiple services.,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.,10,Reduced cost over other technologies but still not cheap enough to make an impact. No easy way to look at the raw data from a GUI. CLI access is required to debug which is not always available for developers. Dramatically reduced the response times for a positive impact on users interactions.,Redis, being our in-memory first storage, has forced us to rethink how we design applications for performance at an even larger scale which has translated into better user interactions and better monetization.,Yes,Product Features Product Usability Product Reputation Analyst Reports Third-party Reviews,Redis has definitely impacted the performance of our applications for the better. It's definitely harder to write code for Redis that it is for other NoSQL databases, but the tradeoff makes it a no brainer.,Couchbase Data Platform, MongoDB and Amazon DynamoDB,Amazon DynamoDB, Couchbase Data Platform, MongoDBRedis is a nice transition to takeWe are a small company with a small engineering team. We are actually DevOps based entirely and working actively with Redis as a key-value storage and a backing service for caching. We love its stability, trustworthiness, and speed.,Basic Storage Caching Queues,Scripting is sometimes cumbersome,8,The primary benefits of Redis are speed and functionality. We drastically monitored increasing throughput and this caused nice feedback from customers.,We transitioned from RDBMS to Redis for performance-sensitive and near real-time data for throughput and simplicity. It has had many positive effects.,Not Sure,Product Usability Product Reputation Vendor Reputation Analyst Reports,Even when working on a distributed network of Redis shards, it is fairly simple with Redis compared to any other alternative when designing and writing largely scaled apps. So, simplified app development was a pro.,PostgreSQL, MySQL and Apache KafkaRedis 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, PostgreSQLThe 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 Beanstalk
Windows, Linux, Mac
Redis
155 Ratings
Score 9.2 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
155 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.2 out of 101

Do you work for this company?

Show Filters 
Hide Filters 
Filter 157 vetted Redis reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-25 of 62)

Companies can't remove reviews or game the system. Here's why.
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
D. Marshall Lemcoe Jr. profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Our organization uses Redis for two main tasks at our organization. First, Redis is used as a traditional in-memory key/store warehouse for a cache system that contains over 400 million items, on average. Using Redis with modern DDR4 memory, we have seen incredible latency savings when it comes to keystore look-ups. Second, we use Redis to manage a distributed queue, such that numerous worker nodes can subscribe to tasks and complete them in an organized way.
  • 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 is the perfect tool if you are looking to increase the speed of a key/value datastore or cache, as well as centralizing your queue management tasks to a dead-simple and incredibly fast database.

That said, it is not well-suited to tasks that have historically been reserved for relational datastores like MySQL or Postgres. Redis lacks relational database features and does not have a dynamic language like SQL to interact with.
Read D. Marshall Lemcoe Jr.'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
Bagaskara Wisnu Gunawan profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Redis is a vital part of our organization as it enables us to process a whole load of queues that our tools have to process. It provides so much value for us since most of our tools require queues to call APIs, etc. We used Redis because of its simplicity of setup and its fast performance. We loved Redis and sure you'd love it too!
  • 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.
It simply has a lot of use cases, but, for our case, we always use Redis for our Laravel queue driver and also for our application's cache driver because it runs so fast and we just couldn't ignore that. We use Redis for dispatch Jobs, storing the cache, working on queues, etc.
Read Bagaskara Wisnu Gunawan's full review
prakash ps profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use redis and recommend for our clients. The key areas Redis outsteps all others are:
1) Scalability
2) Unique and flexible key value db structure
3) They use Ssd Flash for their instances

They also provide session management capabilities to be implemented in any huge projects without much headache. Their db instance also provides a high number of read write per second, which makes it a leader.
  • Session Management
  • Key value pair DB structure
  • High scalability
  • Flash instances
  • Failover Replicas
  • Data Consistency
Redis is particularly suited when you want to mesh millions of data and get a unique statistics or a child dataset out of it. Then Redis is the only viable product with the highest number of read and write per second. It increases my speed drastically so that I am able to put 10k records per second and successfully retrieve at same speed.
Read prakash ps's full review
Bob Bennett profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Redis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to leverage it are continually being investigated and identified. It addresses data consistency and concurrency issues and provides amazing speed to what could be slower operations if handled without it.
  • Cache speed
  • Support for high volume of transactions with elegant handling of data sets
  • Ease of use - well structured and easy to implement
  • Price per shard is a bit high but over all there are no issues worth mentioning
  • I've heard some wishing it supported complex queries but this is asking the solution to support operations it wasn't intended for
Redis is well suited for:
  • Big data manipulation
  • Temporal data index structures
  • Distributed solutions
  • Publish/Subscribe model based solutions
Read Bob Bennett's full review
victor pease solano profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
We used to have most of our web apps accessing our database backend directly, and this was very resource consuming, especially in catalogs and details. This was more critical in our e-commerce storefront. With Redis, we were able to update our webs in order to cache all the queries with resources displayed frequently. In that way, we freed our servers of a huge load. The auto-expire function lets us use the Redis cache and not have to continuously monitor it.
  • 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 is a specialized key-value store, so it's best suited for session variables storage and cache'ing. Redis helps you identify database queries that are repeated exactly the same (for instance, combo lists, product catalogs, configurations, etc).

Redis is atomic, that means you don't have to deal with variables to being blocked to ensure concurrency. So it's great for dashboards, leaderboards, and apps like that.

Redis is not a common database, so don't use it as your repository for data entry or visualization. Yes, it's fast but not that way.
Read victor pease solano's full review
Guljar Prasad profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We are using Redis for one of our clients. We wanted to find a way to handle huge amounts of data for every user search and their MySQL was not able to handle it quickly. We were discussing going more toward NoSQL. After more R&D, we chose Redis. Now it is handling data in an excellent way. It's for a travel product where we are searching hotels and flight for queries given by users, and Redis is rocking here.
  • 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
Read Guljar Prasad's full review
Roberto Luna Rojas profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We are starting to move towards using Redis as our primary storage for performance and simplicity reasons. We have been using it for the last 5 years as a Caching and Session storage mechanism, but last year we started to implement it across multiple services.
  • 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 well suited for applications with well-defined data usage within the NoSQL space, that is counters, queues, leaderboards, time-based, key-value hashes, or for anything that requires many secondary indexes. Still, for a tabular view, a relational DB would make more sense. In the case of full-blown JSON lookup, maybe other NoSQLs could perform as well as Redis.
Read Roberto Luna Rojas's full review
Berkant Ipek profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are a small company with a small engineering team. We are actually DevOps based entirely and working actively with Redis as a key-value storage and a backing service for caching. We love its stability, trustworthiness, and speed.
  • Basic Storage
  • Caching
  • Queues
  • Scripting is sometimes cumbersome
Redis is well suited when a multithreaded environment is needed or you're low on memory resources.
Read Berkant Ipek's full 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
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

Feature Scorecard Summary

Performance (54)
9.3
Availability (54)
8.8
Concurrency (53)
8.8
Security (49)
6.6
Scalability (54)
8.6
Data model flexibility (49)
7.7
Deployment model flexibility (50)
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