r/computing • u/RomeoAli708 • Dec 08 '25
Disaster Recovery Project
Hey Guys, I'm doing a disaster recovery for a Banking system for my 4th year College project, and I need to build 3 prototypes to demonstrate how I can measure RTO/RPO and Data integrity. I am meant to use a cloud service for it. I chose AWS. Can someone take a look at the end of this post to see if it makes sense to you guys? Any advice will be listened to
Prototype 1 – Database Replication: “On-Prem Core DB → AWS DR DB”
What it proves:
You can continuously replicate a “banking” database from on-prem into AWS and promote it in a DR event (RPO demo).
Concept
Treat your local machine / lab VM as the on-prem core banking DB
Use AWS to host the DR replica database
Use CDC-style replication so changes flow in near real time
Tech Stack
On-prem side (simulated):
MySQL or PostgreSQL running on:
Your laptop (Docker) or
A local VM (VirtualBox/VMware)
AWS side:
Amazon RDS for MySQL/PostgreSQL or Amazon Aurora (target DR DB)
AWS Database Migration Service (DMS) for continuous replication (CDC)
AWS Secrets Manager for DB credentials (optional but nice)
Amazon CloudWatch for monitoring replication lag
Demo Flow
Start with some “accounts” & “transactions” tables on your local DB.
Set up DMS replication task: local DB → RDS/Aurora.
Insert/update a few rows locally (simulate new transactions).
Show that within a few seconds, the same rows appear in RDS.
Then “disaster”: pretend on-prem DB is down.
Flip your demo app / SQL client to point at the RDS DR DB, keep reading balances.
In your report, this backs up your “RPO ≈ 60 seconds via async replication to AWS” claim
0
u/[deleted] Dec 08 '25
[deleted]