[10k]: Database (DB) replica

[widal001]

Description

Create a replica of AWS PROD database for legacy grants.gov in a beta.grants.gov environment. Replica should (1) journal all changes from legacy DB to new system DB and (2) support uptime even while legacy DB is undergoing planned or unplanned downtime, maintenance, and upgrades.

The creation of this replica should be scripted using infrastructure as code.

Outcome

• Successful creation of a replica of AWS PROD database for legacy grants.gov in a beta.grants.gov environment to understand how the DB works.
• Ability to perform experiments with the data without impacting production DB
• Understand how future adaptations for our evolving data migration needs

Considerations and Assumptions

• New DB needs to stay in-sync with the legacy DB
• Reliance on expensive Oracle DB
• Changes to the data model require speccing features using the database and we need more info on the issues with the current DB
• Assumptions: When we later want to make changes to the DB, how will that impact Terraform? The service does support changes and we would capture in Terraform.

Dependencies

• AWS Access #139
• [10k]: DB planning #48
• [10k]: Onboard development team #44
• [10k]: Security approval for static site launch #53

Out of Scope

• We will not make changes to the data model in this work

Sub-Tasks

Sub-tasks can be found in this milestone

• [ADR]: Replication tool #322
• AWS dev account to put infrastructure
• Provision infrastructure via Terraform
• Access to MH AWS dev account
• Permissions resolved and access to data

Definition of Done

• Replication of the AWS prod with no changes to the data model
• Replica will support uptime even while legacy DB is undergoing downtime, maintenance, and upgrades
• Changes made to data in the existing production database are available in the new data model in less than 1 hour
• The API endpoints have been tested and verified to return the expected data