Redis Reviews

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.

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.

We are currently using Redis to store sets of object-based information and lists. We query an external system and generate lists in Redis based on the query responses. Because Redis is great at set operations this speeds up the time it takes to make set-based calculations. This Redis cluster supports the a large aspect of the whole application.

Redis is being used by our product engineering team. We use it for caching and as a store for our background processing engine.

We have used Redis in an in-memory key-value store.

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!

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.

Redis is a basic, but extremely fast, key-value storage. We made a decision to use Redis because our use case didn't require a full blown database. We needed something to hold the data temporarily and loss of that data wouldn't lead to any issues. Redis was perfectly fitting our use case, and since then we are a bunch of happy Redis users.

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.

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.

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.

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.

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.

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.

We use Redis for cache storage for data that we need to serve quickly. It is used across the whole organization. It has helped scale up our company and continue to server larger amounts of traffic. Getting data quickly is always a difficult challenge while growing your company, and Redis allows us to serve users quickly and efficiently.

In our organization, Redis is being used as a temporary cache for ephemeral data. This solves the problem of needing to store cached data in a centralized place that is accessible by multiple devices and can be retrieved quickly. In general, nothing is stored in Redis that can't be reproduced from another resource on demand. For example, if we have a process that creates summaries of data from multiple data sources and is costly or very time consuming, we would cache those results in Redis for an appropriate period of time to make it available to other applications in a timely manner without having to rerun the original process. This reduces the time/cost normally incurred to review that data set.

Redis provides support for database analysis and integration of many functions and programs. It is mainly used by our backend team and data analyst. It helped us to grow and expand our business a lot. The tools they provide for the system are the best thing for our organization. Our whole organization is fond of using it and is praiseworthy by our whole team. Many projects that we have done are due to Redis.

We're using Redis in our development department, as a layer on top of regular databases (MongoDB, MySQL), as cache, and for other critical data storage.

In Anzu technologies Pvt Ltd we used Redis for multiple reasons. We developed a social app which allows the user to bookmark the video and internet contents. Performance was an important factor so we implemented user timelines using Redis sorted sets. We implemented the whole notification system using Redis. Our developed micro services architecture using Redis. Caching was another common challenge where Redis performed very well. We just love Redis.

In our project (high load web application with 10k+ users) we used Redis as a user session store, as a distributed cache for web front end servers (with PubSub notifications for changes propagation), and for notification service.

Redis is our primary caching database. We cache most of our intermediate results for backup and scan operations using Redis. Of late, we have also been using it as a message queue. The performance is excellent and features like automatic failover and cluster management are very helpful. All necessary data structures like lists, maps, etc. are supported.

We have a country wide application for generation of an Electronic Way bill for the specific consignment/movement of goods from one place to another, either inter-state or intra-state and of value more than INR 50,000, required under the current GST regime in India typically showing the names of the consignor and consignee, the point of origin of the consignment, its destination, and route. We have specifically used Redis for Caching of user profile information used for authentication of the supplier, recipient, and the transporter. Redis has also been used to cache the Items and their Codes. In the future we also propose to use Redis for authentication and session management. The e-Way Bill replaces the Way Bill, which was a physical document and existed during the VAT regime for the movement of goods. The countrywide roll-out of the e-way bill system is targeted to reduce tax evasion with proper invoicing of the goods and to stop the practice of bogus invoicing of goods. It also plays an important part in the tracking of Goods with the use of robust technology like (RFID) Radio Frequency Identification Devices. Redis was implemented as a cache for all transporter data stored on the GSTN (Good and Services Tax Network). When a transporter entered their GSTIN (Goods and Services Tax ID Number) number into the system, their data was fetched from the cache and used to populate the bulk of the e-way bill.

Redis is used as a cache layer for our high read data as well as a database layer for write-intensive data. It's used in the entire engineering department as the de-facto caching layer for all services being built. The read and write speeds are unmatched because of the simplicity of the design.

Redis is being used extensively by our Web/Cloud department, of which I am a part of. We use Redis essentially for cache'ing but we pretty much try to use it for as much as we possibly can. Almost any information retrieval that we can offload to Redis will save as money, as well as reducing our response times. That is, any time we know that our data requirements are simple enough for a key/value setup to suffice, we use Redis - and in my opinion, anywhere we do not do this is a mistake.

Redis is, at a high-level, an in-memory data store largely setup at a key-value store (although it can persist data to disk, and supports more complex data structures). Redis is generally used as part of a cache layer and has a number of additional use cases that it fills well (messaging and task queues).