I’m a big fan of Fauna. However, I’ve been not been fully comortable relying on it as an app’s primary database.
I’ve experienced rare but multiple instances where transactions have failed because of a service outage. A 15 minute outage can cause hard to fix problems, particularly where later events rely on the transactions that failed during the outage.
If I were to rely on Fauna as my primary database going forward, what would be the best thing to do in this cases like this (short of taking down my entire service)?
I already wrap write queries in a retry function to bypass socket hang up errors, potentially related to node-fetch. So, a solution I’ve been mulling over is to extend this so that transactions that have failed X times get sent somewhere (not Fauna) to be stored, so I can later insert them when Fauna is back up.
Does anyone else have any better ideas?