Share your experience using IBM Cloudant

We use it primarily for real-time applications. In our web application, we added a feature where hundreds of people could play a quiz in real time. 

Instead of using traditional databases like SQL, we implemented Redis to make everything happen in real time – all those quick calculations, data hashing for easy retrieval, and so on. 

It was a live quiz feature, so Redis helped a lot. I also use Redis for caching and similar general use cases.

It improved the performance. For example, data structures like hashmaps in Redis make it a very fast database – much faster than traditional SQL databases. It can perform at significantly higher speeds. Latencies are very low. Our primary focus wasn't on saving money but on improving performance for that specific feature.

So, performance has been the key improvement. Every calculation happened in real time. It improved the performance 10X. 

In our company, we have limited resources, so we can't manage the database ourselves. We use services from Azure for that.  So, Redis integrates well with those services.

We use Azure Cache for Redis.

It performs much better than traditional databases. Our calculations happen in real-time, which was crucial for that quiz feature.

The price could be better. 

I have been using it for more than two years. 

It has been a reliable product for us.

It's been working very well for us. Since our scale isn't huge, it's able to handle our needs without issues.

I've also worked with PostgreSQL, Cassandra, MySQL, and Elasticsearch.

It's tough to find a direct competitor because Redis, Cassandra, PostgreSQL, and Elasticsearch all serve different purposes. Cassandra excels when you structure tables according to your requirements upfront. It offers fast reads. However, the Cassandra Query Language (CQL) isn't as flexible as SQL – there are no joins, for example. It is a very restricted query language. So, we need to carefully design your database tables with future data needs in mind.

Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently.

It's actually quite expensive compared to SQL since Redis uses a system's main RAM, which is costly. And memory can be limited.

We opt for a dedicated server.

Overall, I would rate the solution an eight out of ten. It's been very stable so far and performs well within our system.

I would recommend it, but I would also highlight the cost factor as something to consider.

We have a SaaS-based application. We use the RDS version of SQL Server because it is self-managed by AWS in terms of patch management, SQL server patch management, and OS patch management.

Amazon RDS handles database backup mechanisms and patch management. Since the solution handles OS and database-level patches, we need not worry about security breaches. Amazon RDS has some metrics to show with respect to SQL performance or query running.

I have seen some limitations in Amazon RDS when I try to use SSIS in an RDS world. I need an Active Directory enabled from a security perspective, which was a little painful and cost me extra. There are some advanced monitoring queries that we cannot execute because Amazon doesn't give admin privileges to the end users. We can create another supervisor, but we don't have real admin privileges.

There are some limitations regarding some of the queries and the tools. We tried data replication, and a few features available in an enterprise SQL Server are disabled in the RDS world. We need to upgrade it to an enterprise version. Amazon RDS should improve its metrics a little more.

I have been using Amazon RDS for more than ten years.

Amazon RDS is a very stable solution.

Since it is a SaaS-based application, about 30 to 40 developers are working with Amazon RDS.

We have mostly found the answers to our issues in their forums, but I didn't get a chance to talk to the solution's technical support.

The initial setup of the solution can be done very easily with the click of a button.

Amazon RDS is not a very expensive solution.

Initially, we had an EC2 instance with SQL Server license installed. We had some challenges regarding patch management and backups, and we decided to move to Amazon RDS.

Although Amazon RDS is not a very expensive solution, I would not recommend it for extremely cost-conscious people. Amazon RDS is not a very expensive solution. Amazon RDS is the best solution if you need to quickly turn around an application or product. Amazon RDS is worth the money for me. It is quite easy for a beginner to learn to use Amazon RDS for the first time.

Overall, I rate the solution an eight out of ten.