Amazon RDS Reviews & Insights

RDS is getting used for keeping the application data for multiple microservices. Amazon managed postgres RDS with multiple AZs for High availability. The integration with applications is quote easier with RDS as it provides a cluster endpoint to be used with services

RDS is very well suited for relational data and having a large amount of data and wanted to run sql queries. RDS does provide good monitoring in case of long running queries or queries having locks

Many teams, including mine, use Amazon RDS as an operational data store for applications. Amazon RDS is a great service that provides seamless setup, read replicas, intuitive scale-in and scale-out options, built-in monitoring, and much more.

If your application needs a relational data store and uses other AWS services, AWS RDS is a no-brainer. It offers all the traditional database features, makes it a snap to set up, creates cross-region replication, has advanced security, built-in monitoring, and much more at a very good price. You can also set up streaming to a data lake using various other AWS services on your RDS.

We use RDS for database development and production. Its fully managed capacity and scalability improve productivity and make us tension-free in all environments. I help us create and build instances in seconds, which the teams require, and through which they easily integrate their service with a few clicks.

Based on my 3 years of experience with RDS, I'll recommend that people use it if they need a database as a service in a few clicks to avoid configuration headaches and security issues. When there is a huge amount of data, improvements in sharding for the database are needed.

We started using RDS as an alternative to our BE system since, at the beginning, the team did not have experience or knowledge about BE frameworks, but it was necessary to maintain a relationship between the data of the projects being executed and the RDS services of Amazon were of great help, since it is an out of the box solution. As well as it also served as a starting point to understand how our BE system should be structured later.

For people or companies that are starting out and do not have the necessary concepts to implement a database into their Backend system, or that they don't have their on cluster or a backend engineer that can configure it, RDS can fulfill a percentage of this functionality. Also if later is needed the data can be migrated to a database that lives inside the company cluster.

Amazon Relational Database Service (RDS) is used in our company at quite a large scale. We have migrated all of our server infrastructure to the Amazon Web Services (AWS) cloud, so making use of the Relational Database Service was a no-brainer for us.
Most of our systems are connected to an RDS instance.

Amazon Relational Database Service is a perfect fit for everyone who is seeking for an high-performance cloud-based database service.
No matter if Postgres, Oracle, or any other type of relational database.
Amazon RDS is our first choice for any kind of database requirement in the cloud.
Especially I like the scalability.

In healthcare, managing patient records and sensitive data securely is crucial. RDS offers encrypted storage, ensuring data security and compliance with regulations like HIPAA (Health Insurance Portability and Accountability Act). This encryption extends to data in transit and at rest. With RDS, you can set up multi-AZ (Availability Zone) deployments for high availability. This is vital in healthcare, where database downtime can directly impact patient care. In case of disasters, RDS facilitates quick recovery, minimizing data loss.

Electronic Health Records (EHR) Management: RDS is ideal for managing EHR systems due to its high availability, security features, and scalability. It ensures that patient records are always accessible, secure, and can handle increasing loads as more data is added. For telemedicine platforms that require reliable, scalable databases to manage patient appointments, medical histories, and consultation notes, RDS can provide the necessary backend support. Scenarios Where Amazon RDS Might Be Less Appropriate:Highly Customized Database Configurations If your healthcare application requires very specific, fine-tuned database configurations or uses specialized database features not fully supported by RDS a self-managed database might be a better fit. If your healthcare application requires real-time processing of data (e.g., real-time monitoring of patient vitals), you might need a more specialized solution like Amazon Kinesis or a similar real-time data processing service.

We use RDS to manage all of our SQL databases for multiple billing and payment applications. This includes Aurora and PostgreSQL databases with millions of records and several terabytes of data. These databases are accessed in real time by web applications that handle the requests from thousands of users. RDS handles backups, security, and compliance by default.

RDS is a smart way to deploy and maintain databases in production with world-class capabilities such as backups, scalability, security, and compliance. If you are starting a company or launching a new application, why manage your own database servers? RDS helps you get started with a production-quality database right from the start.

RDS simplifies database management tasks like provisioning, patching, backup, recovery etc. This reduces the administrative burden and allows teams to focus on application development rather than database maintenance. Since this is a managed service it provides in built high availability and scalability. Also we can secure our data by encrypting them at both transit and rest. One more useful use case is, we can selectively encrypt sensitive data to give extra protection

E commerse platforms can take advantage of RDS very well as they have to maintain lot if structured data. I would say if the data is non relational and also if company requires real time analysis and all it is better to use other solutions

Storing relational auditing data for our digital ecosystem which includes desktop website, mobile website and mobile apps to get meaningful insights so as to take next steps.

For storing relational data in a single region across multiple AZ. we can use RDS for any relational data as a matter of fact and it behaves quite well in regards to keeping itself upgrade, salability and in fact availability.

In my organization we use Amazon Relational Database Service (RDS) for storing relational data which is used by our Internal teams for their workloads. In our current use case Amazon RDS addressed the problems of managing the Database, offer scalability and High availability on demand reducing the operational burden on the team.

Best suited - Web applications(when the application need a Scalable relational database with High availability and regional replication), Reporting - You can run SQL queries to create reports out of the data.


Less suited - For large scale unstructured data(Other NoSQL database will be more useful in terms of cost and performance), When you need very low latency in real time.