
- Broke a massive Oracle 11g/12c backed monolith application into 25 microservice‑aligned schemas and migrated everything to Oracle 19c on RDS, giving each service its own performance and scaling boundary.
- What I like most about RDS is that we no longer need to spend a lot of time on manual heavy lifting — patching, automated backups, point-in-time restores (to the second), and even provisioning. Tasks like these used to take weeks, involve multiple meetings, and require approval cycles, but are now fully automated and happen in the background with just a simple configuration.
- The recovery and failover challenges we previously faced with our monolith have been completely eliminated. By leveraging Amazon RDS’s automated, synchronous replication and Multi-AZ failover capabilities, we’ve gained a level of resilience that promises our application stays online even during a full Availability Zone outage. With 99.95% uptime, we are far more than just resilient (In a worst-case failover scenario, the transition happens in roughly 2 minutes, which is well within our acceptable RTO).
- Managing 25 microservices and their rapidly expanding data sets doesn't seem to be a challenge to us, and our operations have been simplified with its configuration-based implementation. With RDS, we have the option to seamlessly scale storage, upgrade instance types, and leverage read replicas to offload traffic. This flexibility has been a cornerstone of our migration journey, delivering significant cost savings and operational efficiency.
- We have the option to stop RDS instances of lower environments during weekends or when not in use, saving additional costs.
- AWS, as usual, has top-notch customer support for RDS. Review collected by and hosted on G2.com.
- Moving from on-prem to RDS broke our deep New Relic integration; because we no longer have OS-level access to install custom agents, we lost the ability to perform granular, table-level monitoring that we relied on for legacy performance tuning.
- We observed that DB gets stuck in the Upgrading/Modifying state during modifications and we really don't have any way to check the actual issue other than just waiting. Sometimes, we are left with just to restart the same, which is quite tedious at times. This really needs some focus from AWS; we, users, need visibility on the progress.
- SYSDBA permissions are restricted, but that's not a blocker. Review collected by and hosted on G2.com.
Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
This reviewer was offered a nominal gift card as thank you for completing this review.
Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review.




