IBM Cloud Databases for Redis Reviews

I have been using IBM Cloud Databases for Redis for the past three years.

My main use cases for IBM Cloud Databases for Redis are caching to improve application performance and reduce load on our primary database. I use it to store frequently accessed data such as user sessions, API responses, and configuration data. This helps us significantly reduce latency and provide a faster user experience.

One specific example of how I use IBM Cloud Databases for Redis for caching is in higher traffic applications. When a user requests product details, instead of querying the main database every time, my workflow operates as follows: the application first checks IBM Cloud Databases for Redis to see if product data is already cached. If it is available, we return the data instantly with low latency. If it is not available, we fetch the data from the primary database and return it to the user, then store it in IBM Cloud Databases for Redis for future requests. I also use a set of TTL values so the cache automatically refreshes after a certain period, ensuring the data stays up to date.

Apart from caching, I also leverage IBM Cloud Databases for Redis in several additional ways. One key use case is session storage, where I keep user session data in IBM Cloud Databases for Redis to ensure quick access and seamless user experience across requests. I also use it for rate limiting and throttling, especially for APIs to prevent abuse and maintain system stability during traffic spikes. Another important use is temporary data storage for asynchronous workflows, such as storing intermediate states or background job processing.

The fully managed nature of IBM Cloud Databases for Redis has had a significant impact on my team's productivity and reliability. Previously, managing infrastructure meant handling patching, backups, failover setup, and monitoring, which took a lot of engineering time. With IBM's managed service, all of that is handled for us. This allowed my team to focus more on building features rather than maintaining the system, and it has also reduced the risk of manual errors during operations. Deployments are faster, and scaling during peak loads is much smoother. From a performance standpoint, the ultra-low latency has directly improved our application experience. For example, in one of our workflows, fetching user session or cache data from IBM Cloud Databases for Redis happens in milliseconds compared to significantly higher latency from the primary databases.

IBM Cloud Databases for Redis has had a very positive impact on my organization across performance, scalability, and operational efficiency. From a performance standpoint, it has significantly reduced application latency, which directly improves user experience and responsiveness. In terms of scalability, it has allowed us to handle high traffic very seamlessly. Operationally, the fully managed aspect has reduced the burden on my engineering team, which is no longer spending time on maintenance tasks such as patching, backup, and failover management. This has contributed to better system reliability and uptime, thanks to the built-in high availability and failover support. Overall, it has helped build a faster, more scalable, and more reliable system, which has improved team efficiency and reduced operational overhead.

I have seen several measurable improvements after adopting IBM Cloud Databases for Redis. From a performance perspective, I observed around 60 to 80% reduction in average API latency for the endpoints that rely on cache data. Requests that typically take 150 to 200 milliseconds from the primary database now take under 20 to 50 milliseconds. This is a huge improvement. I also saw a significant drop in database load of around 40 to 50% fewer read queries hitting my primary database since a large portion of traffic is now served directly from IBM Cloud Databases for Redis. In terms of reliability, I experienced fewer performance-related incidents during peak traffic as IBM Cloud Databases for Redis helped absorb the spike efficiently. This contributed to more stable uptime and a smoother user experience. Infrastructure maintenance effort has also been reduced by roughly 30 to 40%. Overall, the improvement translated into faster response time, better scalability, and improved engineering productivity.

IBM Cloud Databases for Redis offers several powerful features that make it very effective for real-time and high-performance applications. One of the best features is its fully managed nature. IBM handles backup, patching, scaling, and monitoring, so I can focus purely on development instead of infrastructure management. Another key feature is ultra-low latency at high throughput. Since IBM Cloud Databases for Redis is an in-memory store, this allows us to achieve many milliseconds of response time, which is critical for caching and real-time use cases.

My experience with IBM Cloud Databases for Redis has been very positive overall, but there are a few areas I think it could be improved. One area is pricing transparency and cost optimization. While the service is powerful, it can become expensive at scale. More granular pricing control or better cost visibility tools would help teams optimize usage more efficiently. Another improvement would be in monitoring and observability. While basic metrics are available, having more advanced insights, customizable dashboards, and deeper performance analytics would make troubleshooting and optimization easier. I also believe the developer experience with the documentation could be improved.

I have been working for the past three years in my current field.

IBM Cloud Databases for Redis has been generally very stable and reliable, especially for production workloads.

IBM Cloud Databases for Redis is one of my biggest strengths in terms of scalability. It supports elastic scaling, which means I can scale resources such as RAM and storage independently based on my workload requirements. This flexibility helps me optimize both performance and cost as demand changes.

My experience with customer support has generally been positive. One of the key highlights is that the support team is very responsive and knowledgeable.

Before moving to IBM Cloud for IBM Cloud Databases for Redis, I was using a self-hosted IBM Cloud Databases for Redis setup, which was open-source IBM Cloud Databases for Redis deployed on virtual machines. While it worked initially, I started facing challenges as my system scaled, particularly around maintenance, failover management, and backup, ensuring high availability. Managing these aspects required significant engineering efforts and constant monitoring. I decided to switch to IBM Cloud managed IBM Cloud Databases for Redis service primarily to reduce operational overhead and improve reliability. The managed offering provides built-in high availability, automated backup, scaling, and monitoring, which eliminates a lot of manual work.

I have definitely seen a positive ROI from using IBM Cloud Databases for Redis. From a performance standpoint, faster response time improved user experience, which impacts user engagement and retention, especially with high traffic applications. As I mentioned earlier, it has reduced API latency by almost 30 to 40%, and on the cost side, even though there is service cost, it has helped in reducing load on my primary database, which in turn has lowered the scaling costs for those systems. I have also optimized my overall infrastructure spending and observed a positive ROI in terms of engineering productivity.

Before finalizing IBM Cloud Databases for Redis, I evaluated a few other options. I looked at Amazon ElastiCache for IBM Cloud Databases for Redis and Azure Cache for IBM Cloud Databases for Redis as they are well-established managed IBM Cloud Databases for Redis offerings with strong performance and scalability. I also considered continuing with the self-hosted setup, but that would have meant ongoing operational overhead for maintenance, scaling, and failover management. I ultimately chose IBM Cloud because it offered seamless integration with my existing cloud environment along with strong managed capabilities, reliability, and ease of use.

My advice for anyone considering IBM Cloud Databases for Redis would be to first clearly define your use case and workload requirements. If your application needs low latency access, caching, or real-time processing, it is a great fit and can deliver significant performance improvements. I also recommend planning your data strategy carefully. Decide what could be cached, set appropriate TTL values, and avoid loading IBM Cloud Databases for Redis with unnecessary data. Proper caching design will make a big difference in efficiency. Additionally, make sure to implement best practices such as connection pooling, retry mechanisms, and monitoring so your system remains stable under load. I would rate this product an 8 out of 10.

IBM Cloud Databases for Redis is a caching solution for our e-commerce company. The solution can be implemented on websites to reduce page loading time and improve website performance, which is why we purchased this solution.

IBM Cloud Databases for Redis is an in-memory database store solution. It can be used as object caching and for session persistence. If any e-commerce giant implements system design solutions on their website to improve user experience, IBM Cloud Databases for Redis is one segment of that solution.

There are many better solutions available in the market at no cost. Their solution is forked from Waki project. They forked the Redis software and have done far better than Redis.

This solution is not integrated into our website. They asked us to take technical support from a third-party company, which we paid for in addition to paying IBM Cloud Databases for Redis. After several months, it became apparent that there was a technical fault and the solution was not implementable.

IBM Cloud Databases for Redis promised support, guarantees, and solutions, but they did not deliver on any of these promises. Their solution is not implementable on our website. We paid money for something which is freely available in the market, and the paid version is not worth the cost. They also refused to cancel the agreement.

This solution later became open source, yet we are paying for something that is freely available.

I have been using the solution for about nine months.

Our e-commerce company runs 24/7 with 10 to 15 million requests coming from approximately 10 million users.

We have raised support tickets, but they did not provide any assistance. I also raised a support ticket with the AWS team. They do not have a competent technical team and provide minimal support.

Negative

Instead of purchasing IBM Cloud Databases for Redis, you can buy ElastiCache from AWS, which is also built on top of Redis.

They are simply selling false hope to customers, and their solution is neither feasible nor integratable.

The solution is very expensive. The pricing is very high while the quality is very poor.

I would not recommend this product to other users because they do not provide support and give false promises. They do not have any cancellation provision. Better products are available in the market, such as AWS services, which at least provide some level of support.

The solution is very complex and involves multiple vendors. While they claim their product is compatible with everything, when we try to integrate different products with IBM Cloud Databases for Redis, it is not integratable. They claimed compatibility with any website, application, or machine, but in reality, it is not compatible with any of these things.

On a scale of 1-10, this product receives a rating of 1.