Software Engineer at Netaji Subhash Engineering College
Real User
Top 5
Mar 29, 2026
While my overall experience with IBM Cloud Databases for Redis has been positive, there are a few areas it could improve. One challenge is pricing transparency and cost predictability. While the flexibility in scaling is great, it can sometimes be difficult to estimate costs upfront, especially for dynamic workloads. Another area is limited low-level configuration control compared to self-managed Redis. Since it is a managed service, certain advanced tuning options or configurations are restricted, which can be limiting for very specific use cases. I have also noticed that scaling operations can take time, depending on the changes, which may not be ideal during sudden traffic spikes. One area that could be further improved in IBM Cloud Databases for Redis is documentation and the onboarding experience. While the documentation is generally helpful, it can sometimes lack deep real-world examples or best practices for specific use cases including large scaling, caching strategies, eviction policies, or performance tuning. Having more practical guides would make it easier for developers to get started and optimize their setups. Another area is support responsiveness and depth. Basic support is good, but for more complex and performance-related issues, quicker access to more specialized experts would be beneficial. Additionally, improvements in monitoring and debugging tools, such as more detailed insights into cache hit or miss ratios, memory usage patterns, and latency breakdown, would help diagnose and optimize performance more effectively. Overall, enhancing documentation, advanced support, and available tools would make the platform even more robust and developer-friendly, especially for teams running mission-critical workloads.
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.
In-Memory Data Store Services provide ultra-fast data access by storing data in memory rather than on traditional disk-based storage systems. This results in significantly improved application performance and responsiveness.
Leveraging In-Memory Data Store Services, enterprises can achieve high-speed transactions and real-time analytics, crucial for today’s data-driven decision-making processes. These services are particularly effective for applications requiring rapid data access,...
While my overall experience with IBM Cloud Databases for Redis has been positive, there are a few areas it could improve. One challenge is pricing transparency and cost predictability. While the flexibility in scaling is great, it can sometimes be difficult to estimate costs upfront, especially for dynamic workloads. Another area is limited low-level configuration control compared to self-managed Redis. Since it is a managed service, certain advanced tuning options or configurations are restricted, which can be limiting for very specific use cases. I have also noticed that scaling operations can take time, depending on the changes, which may not be ideal during sudden traffic spikes. One area that could be further improved in IBM Cloud Databases for Redis is documentation and the onboarding experience. While the documentation is generally helpful, it can sometimes lack deep real-world examples or best practices for specific use cases including large scaling, caching strategies, eviction policies, or performance tuning. Having more practical guides would make it easier for developers to get started and optimize their setups. Another area is support responsiveness and depth. Basic support is good, but for more complex and performance-related issues, quicker access to more specialized experts would be beneficial. Additionally, improvements in monitoring and debugging tools, such as more detailed insights into cache hit or miss ratios, memory usage patterns, and latency breakdown, would help diagnose and optimize performance more effectively. Overall, enhancing documentation, advanced support, and available tools would make the platform even more robust and developer-friendly, especially for teams running mission-critical workloads.
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.