If you were talking to someone whose organization is considering Amazon RDS, what would you say?
How would you rate it and why? Any other tips or advice?
RDS MySQL (and Postgres) are great managed database services. AWS provides a large range of database instance sizes from micro to very large machines. RDS can scale, and creating Replicas is very easy to accomplish. If you're unsure if you should start using RDS or not, I suggest you consult with a MySQL RDS DBA or Data Architect who has used RDS for several years before making a decision.
On a scale from one to ten, I would give Amazon RDS a ten.
I would rate Amazon RDS an eight out of ten.
On a scale from one to ten, I would give Amazon RDS a seven.
Despite the issues around pricing and technical support, RDS is a good choice for organizations due to the fact that it's very easy to use. I'd recommend it to others due to this ease of use and general stability. Overall, I would rate the solution at a seven out of ten. If they had a free technical support tier I might rate it higher.
For new/existing customers building new products, such as Ola, Uber, or Swiggy, instead of building their own data center first and launching the product which involves massive costs, AWS offers a better quality solution if they are unsure about whether their product will succeed in the market. They can build the product, start making money, and utilize the pay-as-you-go model. Then, they can scale the product depending on demand utilization. That appears to be the best business case for Amazon Web Services.
We have reached the stage where all of our critical applications are hosted on-premises, and the rest is hosted with a public cloud provider. We found that at one stage, it was more advantageous to store some of our core data in our own data centers and have the rest managed. My advice for people who are implementing this solution is to keep in mind that they need to redefine their product. It is not just a copy of an on-premises solution. Rather, it is designed with cloud architecture in mind. We use the term Cloud Adaptiveness. This means that before moving, they need to make sure that the architect of that application, the business owner, and the database administrator all realize that they are going to be migrating to the cloud. They will need to make some modifications before it happens. Otherwise, if they try to do it post-migration, it will be more difficult. I would rate this solution a seven out of ten.
We're currently expanding multiple versions of the solution. We use the cloud deployment model and most clients are also in the AWS environment. I'd advise others to pay attention to the sizing, You don't want to over or under-size. I'd rate the solution eight out of ten.
What do you like most about Amazon RDS?
Thanks for sharing your thoughts with the community!