|
Question: should the FOLIO project use a multi-zone database instance for FOLIO's Jira?
The FOLIO Jira has become crucial to the project's momentum, and the DevOps team has a question about the ideal database configuration. Jira currently uses an AWS `db.m5.xlarge` instance of MySQL in us-east-1d. We can make this database instance multi-zone in the AWS us-east-1 region so the database is constantly replicated to another Availability Zone. In the event of catastrophic failure of `us-east-1d`, we can spin up an EC2 instance in another zone where the MySQL replica is running (e.g., `us-east-1a`). Automatic snapshots of the Jira application/data EBS volume are made twice daily in the event that the EBS volume in `us-east-1d` can't be reached.
The downside is cost. Reserved instance contracts for `db.m5.xlarge` instances are $166/month (about $2,000/year). Making the replicated MySQL instance doubles that cost.
For your information: In the next year or so, the FOLIO project is going to have to move to cloud-hosted Jira and Confluence due to Atlassian's decision to deprecate the self-hosted instances (
FOLIO-3004
Open
).
|