Sign in
Sign in
or
Create a new account
Agent Mode
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Redis Solutions [Private Offer Only]

Carahsoft Technology Corporation

Reviews from AWS customer

6 AWS reviews

External reviews

14 reviews
from

External reviews are not included in the AWS star rating for the product.

3-star reviews ( Show all reviews )

    reviewer2005650

Optimize AI projects with reliable data processing while addressing scaling challenges

  • April 02, 2025
  • Review provided by PeerSpot

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been working with Redis for maybe ten years.

What was my experience with deployment of the solution?

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.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

    Prakasham Dara

Helps to store and load static content for multi-client products

  • May 18, 2024
  • Review from a verified AWS customer

What is our primary use case?

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

What is most valuable?

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. 

What needs improvement?

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. 

How are customer service and support?

I haven't contacted technical support yet. 

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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. 

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)

showing 1 - 2