Redis Reviews

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.

Redis has significantly improved our application performance and scalability. We use it for caching, session storage, and real-time data processing, which has reduced database load, lowered response times, and improved overall system reliability. It’s helped us deliver faster user experiences and handle higher traffic without increasing infrastructure costs.

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 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.

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.

Our organization's main use case for Redis is to store and load static content for our multi-client products.

The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data. 

The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly. 

I haven't contacted technical support yet. 

The tool is open-source. There are no additional costs. 

If you have a large amount of non-dynamic data that needs to be delivered to the client, you should use Redis. I don't think that it will support AI initiatives since it doesn't support continuous data. I rate the overall solution a seven out of ten. 

I am using Redis in a product I have developed.

The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast.

The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud.

I have been using Redis for approximately three months. It provides a database caching user information related to the access token. Mainly for authentication purposes and caching large objects.

I have not noticed any problems with the stability of the solution.

The solution has good scalability.

I have not used the support from Redis.

The initial setup of Redis is simple. The process did not take long and the most time-consuming part was the design phase because you have to use the Ashmap in the proper way.

Redis is an open-source solution. There are not any hidden fees.

My advice to others is if they need a solution for caching or support operations that do not have a lot of relationships in data and you need it for caching purposes Redis is a good choice.

I rate Redis a nine 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.