GBest Practices for Ensuring Data Consistency and Availability
Hi team, I'm building a financial app on Convex where users track spend and borrow, similar to a ledger. Given the critical nature of financial records, I want to make sure that even if the database goes down right after a transaction, no data would be lost.
I have backups enabled, but since they only run once per day, I'm concerned about data between backups.
Are there recommended patterns for writing critical transactions to guarantee durability immediately after a mutation succeeds? Or is there a way to get stronger durability guarantees (e.g., multi-region replication, etc.)?
Thank you.
I have backups enabled, but since they only run once per day, I'm concerned about data between backups.
Are there recommended patterns for writing critical transactions to guarantee durability immediately after a mutation succeeds? Or is there a way to get stronger durability guarantees (e.g., multi-region replication, etc.)?
Thank you.
