Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
IBM Cloud Databases
Score 8.1 out of 10
N/A
IBM Cloud Databases are open source data stores for enterprise application development. Built on a Kubernetes foundation, they offer a database platform for serverless applications. They are designed to scale storage and compute resources seamlessly without being constrained by the limits of a single server. Natively integrated and available in the IBM Cloud console, these databases are now available through a consistent consumption, pricing, and interaction model. They aim to provide a cohesive…
While at the time, Amazon RDS did/does not create Mongo databases, I was able to set up many with PostgreSQL databases with the same ease as IBM Compose. However, IBM compose does seem to offer a more intuitive application control panel. Amazon RDS costs run on a server …
The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go …
MongoDB is the primary db we use, and Meteor is the primary application framework. Configuring MongoDB to fully support Meteor oplog tailing is a challenge - and when we started looking, Compose was those only MongoDB provider that had turnkey support for Meteor.
We use Amazon's RDS (MySQL database), Redislabs (Redis) and also MongoDB's Atlas. They all have their own advantages and disadvantages. For us, MongoDB's Atlas and Compose are obviously similar services. For now, we use Atlas to try new things (since they run the latest stable …
RDS only works if you have access to someone who really knows the product. Don't dabble with RDS - do the full cost-benefit and go all in, if it's what you conclude that you need, including an employee or contractor who has demonstrated rich experience in the product who will actively configure the full product, and deploy monitoring tools to call attention to log alerts, downtime, demand changes and/or cost increases.
I think the best use case for using IBM Cloud Databases is when other products in the IBM Cloud ecosystem are being used. It works very well when computing is being used, or any other IBM cloud products really. I could also see these products being really useful in any scenario where a managed database is wanted with little overhead to set it up and manage it.
Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch
The ease of setup was effortless. For anyone with development experience, a few simple questions such as name and login data will get you set up.
The web application to manage cluster settings, billing settings and even introspect the data was simple and most importantly worked all the time. This can not always be said for web interfaces of other products.
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
Better cost reports, before just increasing to another tier, thus increasing the price. This is critical for early stage startups, where budget is tight.
Add more data center options. As a comparison, a similar service, Aiven.io has dozen more options than Compose (basically all big cloud providers). We moved from AWS to Digital Ocean, which made us stop using Compose, since Compose forces us to be either on IBM or AWS.
We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.
IBM is our trusted partner which never failed to meet our expectations. Stability, efficiency, usability and security is a must have for our business which is fully provided by IBM Cloud Databases
I've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).
We had contacted the AWS technical support request handling team and was a good experience with them. It is very simple to raise a concern request stating your concerns and they are there to help you overcome it within few hours and 1-2 days. Additionally they also provide service/support plan options that can be of help.
Support is helpful enough, but we haven't always had questions answered in a satisfactory manner. At one time we realized that Compose had stopped taking database snapshots on its two-per-day schedule, and had in fact not taken one for many days. Support recognized the problem and it was fixed, but the lack of proactive checks and the inability to share exactly what happened has caused us to look elsewhere for production work loads
During the migration from MySQL installed on Linux to AWS RDS, we were almost surprised as it was done by few clicks rather than too much configurations ans steps in case of traditional DB migrations. In no time our platform was up and running.
The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go for rds.
Increased costs due to having to have a consultant to manage security and more advanced features of AWS and RDS.
The cost of the volume and storage of bds is very competitive with the previous services used.
Its purported Amazon RDS customers can lower their total database operating costs by an average of 40% over three years, achieving a 264% return on investment.