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
Pros
Performance across multiple azs
Query Monitoring with performance insights
Maintaince is reduced as automatically done by amazon
Cons
RDS upgrade using blue green deployment can be made a bit easier. Prerequisites can be made more clearer
Likelihood to Recommend
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.
Pros
Easy and simple setup.
Excellent support for cross region replication.
Enhanced security and access controls.
Multiple instance types based on the need.
Relatively less expensive.
Cons
It could do well to provide tools to update or create database table schemas easily.
Native support to postgres database could benefit.
Likelihood to Recommend
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.
VU
Verified User
Manager in Information Technology (10,001+ employees)
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.
Pros
Scalability.
Fully Management.
Encryption for the databases.
Easy to manage.
Cons
For sure, pricing.
Limited sharding support.
Likelihood to Recommend
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.
VU
Verified User
Engineer in Information Technology (51-200 employees)
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.
Pros
Easy to implement
Lots of documentation and tutorials available, from Amazon and third parties
Low cost
Cons
The official documentation needs to be sharped.
Tools to move data from one server to another
Likelihood to Recommend
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.
Pros
Scalability
Availability
Performance
Cons
Competitive Pricing
Likelihood to Recommend
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.
VU
Verified User
Project Manager in Information Technology (10,001+ employees)
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.
Pros
Automated Backups and Snapshots
Easy Scalability
Read Replicas for Improved Performance
Cons
Limited Control Over Underlying Infrastructure
Cost Management
Complexity in Monitoring and Logging
Likelihood to Recommend
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.
VU
Verified User
Project Manager in Professional Services (10,001+ employees)
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.
Pros
Security
Backups and availability.
Scalability and managing large amounts of data.
Cons
Prices are not cheap.
Logs could be better.
Likelihood to Recommend
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.
VU
Verified User
C-Level Executive in Information Technology (11-50 employees)
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
Pros
Read replicas and global availability of database which enhances user experience
Integrate well with other aws services lile IAM, KMS etc
Performance insight help us to get an aggregate view of db activities which is necessary for troubleshooting
Cons
Introduce more supportive engine
Can introduce more granular control over back ups to save cost
Likelihood to Recommend
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.
Pros
Upgrade
Scaling
Up to date with Oracle
Cons
Upgrade
Replication across regions
Scalability
Likelihood to Recommend
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.
VU
Verified User
Professional in Information Technology (10,001+ employees)
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.
Pros
Scalability - Provide on demand scaling with optimal performance
High availability and Disaster recovery - As a Financial organization we want to maximise our SLO and Amazon RDS helps us by providing HA and DR.
Global reach - As a globally distributed company we want our databases to replicate across regions and Amazon RDS manage that efficiently
Cons
Customization - You can't have a single instance, it will automatically comes with multiple AZ
Better Integration with other AWS services
Likelihood to Recommend
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.
VU
Verified User
Employee in Information Technology (10,001+ employees)
