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
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.
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
I used Amazon Relational Database Service for Databricks Technical Field Telemetry(TFT) Project, which is an internal project for field engineering teams where they manage customer engagement, interactions, feedbacks. This majorly helped to improve our product by managing each team, each individual performances, thus they can set targets for improvement plans. It also displays a hit score which is the benchmark for internal teams. We used Amazon Relational Database Service serverless to deploy the backend database, which is lightening fast, reliable DBMS.
Pros
Serverless
Performance
Scalability
Reliability
Cons
AWS instance downtimes
Ease of use
End user installation
Likelihood to Recommend
It's best suited for serverless computing, really fast, least downtime. But when the Ec2 instance is down it's directly proportional, also we could see a connection issue when Ec2 instance wasn't open.
RDS is pivotal to our data strategy, powering hundreds of databases within our infrastructure. Its reliability and scalability ensure optimal performance and data integrity. Rigorous security measures, including backups and monitoring, maintain database stability. RDS flexibility accommodates evolving business needs while optimizing performance and cost-efficiency.
Pros
Automated Backups
High Availability
Database Snapshots
Security and Compliance
Scalability
Cons
Limited Control
Cost Transparency
Lack of Support for Certain Database Engines
Improved Data Migration Tools
Switch to Encrypted RDS from Unencrypted RDS
Likelihood to Recommend
Amazon RDS is an ideal choice when you need rapid database deployment for your project due to its user-friendly configuration and robust automation support, including Terraform and CloudFormation. Being a managed service, AWS assumes responsibility for its management, ensuring reliability. However, it may not be the best fit if you require extensive control over your databases.
We are using RDS in storing all our products and their information. We have hundreds of brass products and we have maintained all our product database with RDS. It is quick and easy also we have assigned to roles to avoid access to unauthorized users. We have different databases of products depending upon our audience and purpose.
Pros
RDS is fast
All versions of databases engines are already installed
Highly secure
Takes less time to setup
Cons
Logs needs to be more visually appealing and detailed in a proper way
Cost is high
Scaling is an issue, it is tiring and exhausting
Likelihood to Recommend
I am storing structured data such as product description, SKU, price, dimensions, customers reviews etc due to which i need to have structured data therefore relational database is very appropriate for my use case. It becomes very fast. Moreover my setup is in Amazon EC2 thus Amazon RDS has integration for that aswell thus making it a perfect combo.
Amazon RDS helps set up, run, and grow relational databases in the cloud with the aid of Amazon RDS, a managed relational database service provided by Amazon Web Services (AWS). There are several, but I'd want to focus on the most significant ones. a)global Scope b)cost-effectiveness c)Security and many more
Pros
Global Reach can be possible because of this
Cost saving, not too much expensive.
Data backup and recovery
High availability
Cons
It can add more advanced security auditing.
Transfer from RDS to another database is complex, it can be improves.
Frequent UI changes make daily work a little more challenging until we become accustomed to the New UI. However, there is always a choice to return to the previous user interface.
Must support all types of famous databases.
Likelihood to Recommend
#It is most suitable and proper for web applications where we use RDBMS(Relational database). #E-Commerce Platforms: Because RDS is scalable and can handle changing workloads during sales events or seasonal traffic spikes, e-commerce platforms, and online retailers can profit from it. #RDS can offer a safe and scalable alternative for mobile apps that frequently need a backend database for user data.
*Not well managed on the migration of databases. *RDS does not support advanced features that are unique to some database engines.
We need to store the persistent data such as order information and other insurance related information in a database for which we use Amazon RDS. Our business revolves around being able to store the order data and keep it in sync with the real time changes in order data and then finally get an outcome for that order. RDS has been a service of choice for us as it has high concurrency and low latency as well as disaster recovery built into it.
Pros
Securely storing the data with high concurrency
Replication of the data to another Availability Zone for disaster recovery
Taking backups and snapshots for data recovery
Cons
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
Likelihood to Recommend
When we need to store the data that is structured and we know the format of the new entries then it is best to use Amazon RDS as a cloud service. It may not be well suited when the data is not structured and the new entries may have a different format.
We get huge amount of data for market research and data grows day to day. We found Amazon Relational Database Service (RDS) was a best solution to handle such huge data and till now we are good at performance and handling the data
Pros
High Performance
Storage
Security
Cons
Database Log Shipping
Server Level Triggers
Custom password policies
Likelihood to Recommend
Well suited : If you are handling huge data and want to give high performance and also do scrubbing to the data based on the requirements
Less Approproiate : Machine Learning and R Services are not available in Amazon Relational Database Service (RDS), Limited support for Linked Servers
We use Amazon Relational Database Service (RDS) as our main database to store daily data from our application. We need to store different kind of data generated from our application and we need to ensure it is always available and with multiple layers of security/redundancy to avoid downtime and to comply with compliance standards.
Pros
SQL data
Backup
Management
Cons
Monitoring
Audit
User management
Likelihood to Recommend
If you need a SQL database Amazon Relational Database Service (RDS) provides multiple options for all flavors. It also delivers easy management and pretty decent speeds. If you have non relational data then it is better to avoid it instead of making workarounds to make it work. Today some of the RDS options do offer more modern data structure and might fit.
