Whether your organization is [an] early startup or large company AWS RDS fits in most of the cases such as 1. Easy to start, setup, used by [a] few or large developers team. 2. You can easily scale DB [instances] when your business required scaling as a startup or pay only for [users] to optimize cost as [a] large organization. 3. If your application requires SQL Server, Oracle, or Maria DB then you should use AWS RDS instance. 4. Your application requires better availability and security of data you can use AWS RDS instance. When AWS RDS is not recommended: 1. You need automatic scaling or capacity flexibility as request load gradually increases, better to use Amazon Aurora DB in this case.
Well suited for: Games, Chat rooms, real time software like corporate events, marathons and so. Anytime and anywhere you could use a NoSQL DB you should think of SimpleDB.
As an arduous AWS user, Amazon SimpleDB easily integrates with EC2 and other AWS module; and if you are not an AWS user, you also have a fantastic tool that will solve the problem for which you are focused.
You don't have os-level or hardware-level access to the system, so all your performance tuning needs to be done within your application or within the parameters of the database engine that amazon allows you to customize.
Customizations/Extensions to the database engines are impossible, as you don't have OS-level access.
Migrating in/out of RDS with zero down time can be relatively challenging from a configuration and execution perspective, depending on your infrastructure.
It has worked reliably in the past, we have not had any problems that would have been caused because of using RDS. Also it's future-proof, it will scale easily if user base of the application that relies on it is going to increase rapidly. Our application deployments also rely on it so renewing it is essential for business & switching to different provider would cause costs without any apparent benefit.
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).
I have only had good experiences in working with AWS support. I will admit that my experience comes from the benefit of having a premium tier of support but even working with free-tier accounts I have not had problems getting help with AWS products when needed. And most often, the docs do a pretty good job of explaining how to operate a service so a quick spin through the docs has been useful in solving problems.
[Amazon Relational Database Service (RDS)] is much better to have everything in the cloud instead of having it on-premise once you can get all the benefits from Cloud. Of course, it can be a bit expensive if your company it's not growing anymore but if you check it in detail, you can see that the scalability of Cloud makes a lot of sense and also the reliability.
It integrates beautifully with AWS. In some projects we use SimpleDB while we use DynamoDB for others, according to the characteristics of the project. If the infrastructure is AWS, we always think of one of them.
RDS has made sure that we don't spend a lot of time resolving issues that are not even remotely relevant to our business use-cases. It has thus made the life of DB administrators easy which allows them to explore other avenues as well.
Using RDS for around 10 years now, we have never had an issue BECAUSE of RDS. It is a very reliable service.
