Best 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.
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Hi! Convex is multi-AZ out of the box, but not multi-region. You want to account for the loss of all of us-east?
thanks, jamie! i think that's sufficient! would handling an AZ failure be something we need to account for in our design?
if a malicious actor clicks on "delete project" button, is there a way i can recover the data?
is there sth like a
Point-in-Time Recovery that the convex team can help us out with?