Overall Satisfaction with Amazon Relational Database Service
We used Amazon Relational Database Service to administer an SQL Server versus hosting it on site. This was a project aimed at testing functionality for a highly available failover HL7 system. It met our expectations for managing the database for this application. When we were finished with this Proof of Concept project we decided the latency was too great at the moment and would wait for improved infrastructure improvements to the AWS Cloud. The best part of the whole exercise is that we were able to terminate the instance and only run it while we were testing. No major infrastructure investment was required other than the time we used the instance.
- It is flexible for when you need it and how you need it. You can configure it to meet your requirements for performance and relaibility.
- Ease of set up, just a few clicks with a secure communication.
- The ability for use over our VPN by name versus IP would have been one of the features we would have liked to have.
- These are still in development, no negative impact. When we had to stop using the RDS it actually saved us money versus our other options.
- Azure SQL Database and Amazon Relational Database Service
Azure and AWS RDS are very similar, both have similar capabilities and functions. When you need it, the aspect of only being charged for a running instance is very nice.