Redis Cloud Pay as you go with 14-day Free Trial

What do you like best about the product?

The each entry of Redis cashes to maintain ttl for long time as per our request

What do you dislike about the product?

The maintenance window which was managed by Redis team

What problems is the product solving and how is that benefiting you?

Redis Cloud is solving several critical problems that developers and businesses face when managing high-performance, real-time applications.

We use Redis  for several purposes, including ranking, counting, saving, sharing, caching, and setting time-to-live notifications. These functionalities are employed across various AI projects and in data processing tools, where Redis  helps with the ongoing data pipeline process.

Redis has multiple valuable features such as being a free and reliable open-source tool. It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes. Despite its limitations, Redis provides valuable performance enhancement through system fine-tuning and multi-thread handling.

There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and systems. Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active. There's a need for better migration tools to support data movements in a hybrid environment. Concerns exist about licensing and community engagement due to changes in Redis and its forks.

I have been working with Redis for maybe ten years.

We encountered several challenges during the deployment process. Redis required a comprehensive setup process, with attention to hosting parameters, environment preparation, and network rules configuration. It is particularly complex in high-performance scalability contexts, taking us around one week to deploy initially.

Redis is fairly stable, although improvements are needed concerning user load and direct answering time, which sometimes results in downtime on the user side.

Redis is somewhat limited in scalability, rating around four or five. Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.

We have been using Redis since before I joined the company, so I am unaware of any previous solutions.

The initial setup of Redis was difficult, with a rating of two or three out of ten. A deep understanding of Redis’s core and high technical knowledge was required, making the process lengthy and complex.

Our implementation was handled internally by a small team. Typically, deploying Redis requires participation from around two or three people.

Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses. The solution is integrated and utilized internally without financial investment.

We did not evaluate other solutions before selecting Redis, as it was already decided by the time I joined the company.

I rate Redis seven out of ten overall. While it's a powerful open-source tool, it has areas needing improvement in terms of scalability and certain functionalities. Despite this, the tool provides reliability for our needs. I recommend considering these aspects before adopting Redis for large-scale operations, especially if high technical competencies are needed.

Hybrid Cloud

I use Redis  as a tool in building projects, specifically for in-memory caching. My backend API uses Redis  to cache information retrieved from the database.

Redis acts as an in-memory search tool that improves the speed of operations. By making operations faster, Redis allows for quicker data retrieval and enhances the performance of applications.

Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation. 

Additionally, better documentation is needed to set up a secure Redis server with user authentication, as there are gaps and issues in this area.

I have been using Redis for two to three projects recently, with a total experience of about five to six years.

Redis is quite mature and stable, and I haven't encountered any stability issues.

Redis does not require scaling. It can be a central in-memory store for all scalable units of an application, and it is not necessary to have a duplicate copy of Redis.

The setup is quite easy; I would rate it as eight out of ten. However, there might be some difficulties related to secure servers.

Redis is a free tool available for on-premises installations. There's no cost associated with it as I haven't used any cloud services.

Redis is a nice choice for building applications that require high turnaround times for user requests. It reduces turnaround time by building a cache solution based on Redis. 

I rate it as eight out of ten.

I use Redis  as a cache to store user sessions with login details and also some current status of the devices.

The performance of Redis  is very fast. Its deployment is pretty easy when using it on ElasticCache, and I did not need to worry about scalability on AWS . It's pretty scalable and stable.

For the PubSub feature, we had to create our own tools to monitor the events.

I have been using Redis for about six years.

The ElasticCache is pretty stable.

I did not need to worry about it on AWS , so it's pretty scalable.

I have never contacted the Redis support team.

Positive

I would probably advise learning how to use command-line tools.

I'd rate the solution eight out of ten.

Public Cloud

Amazon Web Services (AWS)

In my current workplace, we use Redis  for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking. 

Previously, at another company, we used Redis  to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.

In my current workplace, we use Redis for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking. 

Previously, at another company, we used Redis to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.

Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle. We primarily use Redis as a caching system due to its multiple data types and PubSub features, offering efficient data handling. Redis's PubSub capabilities benefit our communication by facilitating thread intercommunication. It allows multiple threads to exchange messages efficiently.

Redis presents a single point of failure and lacks fault tolerance. It would be beneficial if high availability features were available in the noncommercial version, similar to those offered by the commercial managed solutions from Redis Labs.

I have been working with Redis for over ten years.

If Redis is set up correctly, it requires no maintenance and can function smoothly for long periods without intervention. Memory calculations should be precise to avoid issues.

With approximately 500 microservices and environments scaling up to 1,000 customers, Redis accommodates a range of scales. Proper memory allocation allows for seamless operation.

We have not utilized customer support for Redis.

Positive

In comparison to other caching solutions like Memcached and Aerospike, Redis is easier to deploy and manage. Aerospike, while highly efficient, is more complex to set up.

The initial setup of Redis is very straightforward and user-friendly. Deploying Redis takes about thirty seconds, making it quick and efficient.

Implementation can be done in-house using AWS  ElasticCache or Docker  to run Redis on Kubernetes , depending on cost and environmental factors.

We use Kafka for inter-process communication, but Redis is used for thread intercommunication due to its PubSub capabilities.

I recommend Redis as it provides an easy-to-use caching solution with beneficial PubSub features. 

It's excellent for startups or new projects with many components needing coordination. However, for more advanced messaging or larger data volumes, Redis might not be the best fit. 

I rate Redis a nine out of ten.

Hybrid Cloud

Other