Redis Reviews

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'm the only user utilizing Redis in my company, as my platform is relatively new and has around fifty users. However, in my previous role at Profit Clicks, we had approximately ten thousand users. We utilized a combination of databases, including Redis, MongoDB, and MariaDB. We needed to handle push notifications for our users, sending them three times a day, and managing a large volume of notifications efficiently was crucial. Redis played a role in managing this workload.

I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios.

There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient.

I have been working with Redis for the last year approximately.

Redis is stable and works well without any issues on my end. I occasionally encounter problems with MongoDB because MongoDB has a very different stack.

It is a scalable solution.

Redis requires occasional maintenance, but it is generally a low-maintenance solution and is straightforward to manage. I haven't encountered any difficulties or downtime after updates, as Redis is robust and concise.

I haven't explored AI-driven initiatives yet, but they are on my road map. I would recommend Redis for all kinds of caching and message brokering needs. It's a reliable and straightforward solution.

Overall, I would rate Redis ten out of ten.

I use the solution for saving user sessions and user data for different applications.

The online interface is very fast and easy to use.

There is a lack of documentation on the scalability of the solution. 

The product should create awareness about its scalability.

I have been using the solution for five years.

The solution is very stable.

The product is very scalable.

The initial setup is easy.

The deployment could take one to two weeks.

People using the solution should be aware of all the features of the solution. Overall, I rate the solution a ten out of ten.

It was a classic caching use case. In my previous company, we were running MongoDB on the cloud, and we were running Redis for caching. We were just starting, so the data size was pretty small there.

We were caching the data, and it was helpful in terms of speed. It uses the key-value method for storing the data, and everything lives in memory, so it helps with the speed. Solutions such as Redis, or Memcached, are helpful for fast access.

The in-memory data makes it fast.

I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources. I believe as the Redis ecosystem grows, over time, there will be more adoption, and its community will grow. There will be more resources available for support and questions.

In terms of features, they are doing a good job and coming up with many new features, such as Redis Search. They have also introduced a new cloud service. However, I haven't used it much, and I'm not that familiar with the Redis ecosystem, so I don't have input on the features they need to build or improve.

I'd rate it an eight out of ten because it did what I needed, and it did a good job. However, currently, not every product in the Redis ecosystem has a great community or great support.

We use Redis for caching and to improve the speed of the database. 

The product offers fast access to my database. 

I have been working with the product since 2022. 

Since implementing the product, we have experienced stability in our applications.

The solution is scalable. 

The initial setup took some time as our technical team needed to familiarize themselves with Redis. Once they gained expertise, the deployment process became straightforward and was completed within a month and a half. A seven-member team helped with the deployment. 

Redis is an open-source product. 

I rate the product an eight out of ten. 

In the past, I used Redis as a cache, and currently, I'm using it as a messaging system.

Redis is pretty fast compared to others, making it a reliable choice. It's much more reliable and helps with our message broker functionalities.

Redis is a single thread, which is one of the key features I like. Redis is also pretty fast, and many of our use cases are satisfied with its single-threaded nature. This feature helps us manage concurrency effectively.

I don't think there's any room for improvement as it's been good for large-scale use and large datasets.

I have been using Redis for almost three years now.

I haven't faced any issues from a performance, outage, or availability point of view. It's good.

It's very easy to scale up and scale down. I'd say it's highly scalable.

I didn't get a chance to interact with their support team.

Positive

Use Redis wisely because it is a single-threaded tool. There was an issue we faced in the past where a query was not optimized, which impacted performance significantly.

I've used Redis mainly to improve application performance through caching. I've also used it as a small project broker and an external lock mechanism. I used it in previous companies. 

What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting.

I have been using the solution for eight years. 

I haven't faced any stability issues. 

I rate the tool's scalability an eight out of ten. 

Redis is an open-source solution. 

I rate the overall solution a ten out of ten.