3 ms·
The solution I would have gone through (granted, in a very different industry, finance is quite different from developer SaaS) would probably be closest to #4:
by PeterisP 8y ago
The solution I would have gone through (granted, in a very different industry, finance is quite different from developer SaaS) would probably be closest to #4: identify the writes that we're about to lose; get all the account/user ids somehow related to these writes, back up everything that needs to be backed up and then go ahead, "lose" that data in the live system, bring the site up while blocking only the involved accounts until data is manually reconciled from backups. Granted, this requires the possibility for some separation so that you actually can selectively make some customers data fully inaccessible so that other writes wouldn't affect it, but it seems reasonable for github because datasets are mostly isolated/grouped in repositories.
10000 writes can be manually reconciled, been there done that, and the number of users that it affects is small enough that it's not appropriate to keep the site down for everyone for a day if you can rather keep it down for 2 days for a small number of users that you can contact (and compensate!) separately; the downtime for the unaffected users could be significantly reduced that way.