Payments will gown down in flames if the fr-write database goes away, we should provide redundancy. The only requirement is a connection for contribution tracking.
- Maybe create a c_t table on payments1 with an auto-increment way above the threshold and backfill once db1008 comes back? - Wait, do you mean backfill the real c_t table, and nuke the table on payments1?
- Start using UUIDs so this requirement no longer exists - I feel like I'm failing to remember some shining good reason this won't work either.
- Recent contribution_tracking can be served using a redundant key/value store such as Redis. Archived contribution_tracking can still be served from mysql.