I used Redis for a one-time implementation while working on a college project. I implemented it locally on a machine and used it for a vector search.
External reviews
External reviews are not included in the AWS star rating for the product.
Does not work with AWS
I tried to sign up with AWS through Redislabs.com and once I've subscribed through amazon i tried to set up my account and redis does not recognize my email. What the heck?
Fast reliable solution that provides consistent results for university project success
What is our primary use case?
How has it helped my organization?
Since it was a university project, it helped in providing a stable and efficient solution for my project needs. This enabled me to complete the project successfully and pass an exam.
What is most valuable?
Redis is stable, provides consistent results, and is fast. It is particularly efficient for cloud-based storage and operations.
What needs improvement?
Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud. It would be helpful if Redis could provide a one-stop solution for all data varieties, which would improve the integrity between different databases.
For how long have I used the solution?
I used Redis for about a day for the implementation.
What do I think about the stability of the solution?
Redis is definitely a stable product. It provided accurate and consistent results without any issues.
What do I think about the scalability of the solution?
Redis is a highly scalable product, especially since it effectively handles cloud-based storage, which is the most scalable option.
How are customer service and support?
I did not communicate with the technical support team, so I cannot provide a rating for customer service.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I also used Firest for my project and found it to be more suitable for my specific use case.
How was the initial setup?
The initial setup was very easy. The only requirement was to change the syntax from Redis to Firest and vice versa.
What about the implementation team?
I completed the implementation all by myself without needing any additional help.
What's my experience with pricing, setup cost, and licensing?
I used the free, open-source version of Redis, so I did not incur any costs. For personal use, a lower price is always better.
Which other solutions did I evaluate?
I evaluated and used Firest and several other databases for my project, including Crontabee and Cosmodb.
What other advice do I have?
Redis is beneficial for specific usage and domains. If Redis can handle various data types efficiently, it would become a comprehensive solution for any use case, potentially topping other databases. Its consistent results and free, open-source nature make it a solid choice.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Fast single-threaded solution for large datasets and effective concurrency management
What is our primary use case?
In the past, I used Redis as a cache, and currently, I'm using it as a messaging system.
How has it helped my organization?
Redis is pretty fast compared to others, making it a reliable choice. It's much more reliable and helps with our message broker functionalities.
What is most valuable?
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.
What needs improvement?
I don't think there's any room for improvement as it's been good for large-scale use and large datasets.
For how long have I used the solution?
I have been using Redis for almost three years now.
What do I think about the stability of the solution?
I haven't faced any issues from a performance, outage, or availability point of view. It's good.
What do I think about the scalability of the solution?
It's very easy to scale up and scale down. I'd say it's highly scalable.
How are customer service and support?
I didn't get a chance to interact with their support team.
How would you rate customer service and support?
Positive
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Has interesting algorithms like HyperLogLog and provides useful features
What is our primary use case?
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 is most valuable?
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.
For how long have I used the solution?
I have been using the solution for eight years.
What do I think about the stability of the solution?
I haven't faced any stability issues.
What do I think about the scalability of the solution?
I rate the tool's scalability an eight out of ten.
What's my experience with pricing, setup cost, and licensing?
Redis is an open-source solution.
What other advice do I have?
I rate the overall solution a ten out of ten.
Used for data deduplication or identifying duplicate records
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
The solution's pricing for a local installation is very expensive.
For how long have I used the solution?
I have been using Redis for three years.
What do I think about the stability of the solution?
I haven’t faced any issues with the solution’s stability.
What do I think about the scalability of the solution?
Azure allows Redis to scale. If I want, I can increase the resources allocated for this service.
How was the initial setup?
I'm using the solution as an Azure cloud service with no installation involved.
What was our ROI?
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.
What other advice do I have?
Overall, I rate the solution ten out of ten.
A simple open source solution with good caching capabilities and managing key-value pairs for handling cache requests effectively
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Redis for the last year approximately.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
It is a scalable solution.
How was the initial setup?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Used to cache repeated data and provides clear documentation
What is most valuable?
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.
For how long have I used the solution?
I have been using Redis for four years.
What do I think about the stability of the solution?
I haven’t faced any stability issues with the solution.
What do I think about the scalability of the solution?
I have never faced any issues with the solution’s scalability.
How was the initial setup?
The solution is easy to set up and has very clear documentation.
What about the implementation team?
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.
What other advice do I have?
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.
Helps to store and load static content for multi-client products
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?
Enables efficient caching and helps users fetch and save data quickly
What is our primary use case?
We use the solution as a caching layer.
What is most valuable?
The ability to fetch and save data quickly is valuable. We can fetch data within milliseconds. The tool provides data structure capabilities. It also provides geolocation search and JSON search capabilities. The performance is very good. Redis can save each internal transaction to the file system. It helps us handle persistence in our storage.
What needs improvement?
The product's main purpose is caching, even though the vendor says we can also use it as a persistent database. If we use a lot of data, it will eventually cost us a lot. The tool is single-threaded. It doesn't support many data models. We only have key-value, hash, and JSON.
For how long have I used the solution?
I have been using the solution for more than ten years.
What do I think about the stability of the solution?
The tool is stable.
What do I think about the scalability of the solution?
The tool is easy to scale. We can add additional storage, and it will scale easily. We have millions of end users. We are an enterprise-level organization.
How are customer service and support?
The product provides excellent support.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment is easy. The deployment takes a couple of hours. One engineer can deploy the tool. We can fully manage the tool as SaaS with low maintenance. If we want to deploy it in our own environment, we must be more aware of changes and monitoring. Since I'm using the caching layer, we must choose the correct mode to save and fetch the data optimally. It is complicated to understand which feature or model we must use.
What was our ROI?
Eventually, we need to manage caching. If we manage on our own, it will take a lot of developer resources, infrastructure, and environmental resources. So, it is better to use Redis. The ROI is better.
What's my experience with pricing, setup cost, and licensing?
We pay a yearly fee, but we pay according to the usage.
Which other solutions did I evaluate?
I also work with PostgreSQL, MySQL, Elasticsearch, Cassandra, and Splunk. Redis provides efficient caching and performance. The other solutions have persistent storage functionality. If I want persistence, I would use the other tools. If I need high performance, I would use Redis.
What other advice do I have?
We must understand our system needs and pick the correct data structure in Redis to support it most efficiently. Overall, I rate the tool an eight out of ten.
My Experience Using Redis Enterprise
It stores your data in RAM for Faster read and write operations.
Redis Enterprise has multiple features for faster data Accessibility, Security, Performance and Loss of Data Security (Data Durability).
Features like active-active and active-passive replication ensure that data is always avalilabe in case of faliure.
Rules are easily configuralble to ensure unwanted data deletion, to take timely data dump in case of machine faliure.
Usig Redis to cache static data for your application can take off load from your database and make your application feel much faster
It also cannot build complex data relationships as it uses key value pair to store data.