Redis Reviews

Sometimes, Redis is used as a cache and sometimes as the main database.

Redis is a simple, powerful, and fast solution.

Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application.

I have been using Redis for three years.

I rate Redis a seven or eight out of ten for stability.

In our team, around 20 to 25 engineers are using the solution.

I rate Redis a nine or ten out of ten for scalability.

The solution's technical support team was quite knowledgeable and fast.

Positive

We previously used other solutions like DynamoDB, Elasticsearch, and Postgres for different use cases. We switched to Redis because maintaining the cluster for Elasticsearch was very complex and a lot of work. Also, the other solutions were very, very expensive.

The solution’s initial setup is easy.

Since we're using the AWS self-managed version, Redis can be deployed very fast if you go through the console. If you do an infrastructure, its setup will take longer. But if you just want to play with it and set it up quickly, it can be done in 10 to 15 minutes or less.

The solution's pricing is good compared to other databases doing the same thing. It might be cheaper to use Redis in some cases and not in others. Redis is not an overpriced solution.

Redis is deployed on-cloud in our organization.

When it started, Redis had a very simple structure, but now it has a lot of powerful data structures. Users should investigate because they can use other things for their data structure. Redis has more new use cases. Users must consider that Redis is single-threaded, which might take a toll on them when they write to Redis. This might be an issue if you need very high throughput with writes.

Overall, I rate Redis a nine out of ten.

I use Redis for distributed caching management. Additionally, I sometimes use it for Pub/Sub mechanisms.

Redis is good for distributed caching management. It provides a faster way to access data compared to SQL Server caching management, making it preferable for caching.

Redis should have an option to operate without Docker on a local PC. That would be beneficial for me.

I have been using Redis for five years.

Sometimes Redis has issues with TBS, which affect its performance. However, I think these might be due to improper setup on my end. Based on stability, I would rate Redis a six or seven out of ten.

I have never had to contact the support team for any reason.

Positive

Before using Redis, I used NCache and SQL Server Cache.

The pricing for Redis is average compared to other solutions, and it's more cost-effective than SQL Server caching management for my purposes.

Redis Cache is better than other competitors and I would recommend it to other people.

I'd rate the solution nine 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 have been using a specific infrastructure. We use it primarily for customer service.

It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology.

The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier. But no one provided a GUI, or maybe we didn't request it. I'm not sure. We just make use of it.

My experience with this product has been very good.

It's been very stable. I would rate the stability a ten out of ten. 

We saw an ROI. It made the processing of our transactions faster.  So there are some details we get, like customer contract details, customer details, customer ID, there are so many details for that.  So we get it from Redis, which makes it faster.

I would rate it an eight out of ten.

I would recommend to explore this product as it's gonna make the work easy.

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. 

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.

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.

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.