Redis Reviews

I primarily use Redis as a cache to store the most requested files, folders, and URLs. This makes retrieval fast and has minimal latency.

Redis is a simple service that does what it promises. We use it through AWS, and it's not managed by us. There is no operational overhead thanks to Amazon. It is highly available, reliable, and functions exactly as expected, eliminating the need to reinvent the wheel with cache.

There is room for AWS to provide more options for server types or a way to configure more or less memory for them.

I have been using Redis for about four years.

Redis is 100% stable for our needs. We haven't experienced any complaints or issues related to stability.

AWS allows you to change the cluster size for Redis easily. However, I am unsure if horizontal scaling is possible.

Using AWS for Redis, the setup involves going through a user-friendly UI, making the process simple and straightforward. After setup, you get an endpoint, and it's ready to use.

We use Redis through AWS, so we pay related costs monthly as specified by Amazon.

I rate Redis a ten out of ten. There might be some improvement needed by allowing more configuration options regarding resources available for the servers.

I use Redis for data deduplication or identifying duplicate records I receive. I have a very basic usage with Redis, where I insert a key value record.

The solution is fast, provides good performance, and is not too expensive. Although installing it locally would probably be cheaper, I don't want the hassle. For the functionality I need, Redis gives me what I want at the moment.

The solution's pricing for a local installation is very expensive.

I have been using Redis for three years.

I haven’t faced any issues with the solution’s stability.

Azure allows Redis to scale. If I want, I can increase the resources allocated for this service.

I'm using the solution as an Azure cloud service with no installation involved.

The solution does what I need, and I have no issues with it. Since I didn't install Redis and don't need to maintain it, the service saves me a lot of time.

Overall, I rate the solution ten out of ten.

In our company, Redis is used for read operations. When we receive data from a user via the Read API, we cache the response for two or three minutes to minimize API calls to the database and preserve resources within the DB. This practice also helps prevent bot-triggered dummy requests to the DB.

One crucial aspect is that Redis ensures that the response time does not exceed one second. Redis can be highly beneficial for both the user and customer-facing applications in this regard since it prevents any potential lag in the user-facing application.

Redis itself is a feature. In Redis, the memory store is in-memory and not on the disk, making the solution fast. Also, retrieval is super fast in Redis.

There isn't any scope for improvement in Redis since its functionality is limited to read operations only.

In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality.

I have been using Redis for four years. Also, I don't remember the version of the solution I am using.

Though the solution is stable, its stability is something that depends upon the infrastructure of the company where it is being used.

It is a scalable solution, but we don't have any plans to increase its usage.

The solution's technical support team is good. Also, we have an in-house team in our company to help us.

The solution's initial setup process was straightforward. Also, the solution is deployed on the cloud.

I would recommend this solution to those who extensively rely on read operations. Overall, I rate the solution a nine out of ten.

I use Redis mostly to cache repeated data that is required. If I'm using a user wallet address, I don't need to call it all the time from the database. I do the cache using the solution.

The solution allows you to create a message of application publishing and messaging the application in other services. It helps a lot when I work with the microservice architecture.

I have been using Redis for four years.

I haven’t faced any stability issues with the solution.

I have never faced any issues with the solution’s scalability.

The solution is easy to set up and has very clear documentation.

To deploy Redis, you need knowledge about JavaScript, programming, and how data structures are stored. It takes around five to ten minutes to deploy the solution.

With Redis, I can create lists and key-value pairs. The solution also provides many features for storing data in cache. Storing data in memory using Redis is faster than using traditional databases like Postgres or MySQL.

If you are communicating with the services, you can use the solution's Pub/Sub capabilities to send messages, store data in cache, and share it with other microservices. The solution's data persistence model has greatly benefited our resilience, especially when storing any key-value pair.

You can install the solution on the local machine or cloud servers like AWS or Google Cloud. I would recommend Redis to other users.

Overall, I rate the solution a 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.

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