Anyone else find this scheme completely atrocious?
1. Relying on a home computer on the critical path for data backup and persistence for a business
2. Relying on a high latency, low quality networking path between the slave db and the 'home mac' rather than a more reliable link between two machines in a datacenter.
3. A poor persistence model for long lived backups
4. No easy way to programatically recover old backups
What's even more disturbing is that this isn't a new problem. Its not like we don't know how to backup databases. This solution seems very poorly though out.
The biggest source of credit card fraud is that there's no standard way of proving that someone is in physical possession of the card.
Online transactions only require CC#/Exp/CV2 name/address etc which are stored on merchant machines and then compromised and released to the while.
A much more secure option would be to have CCs with built-in RSA key gen. Stealing the CC#s would no longer be enough to make a fraudulent transaction.
1. Relying on a home computer on the critical path for data backup and persistence for a business
2. Relying on a high latency, low quality networking path between the slave db and the 'home mac' rather than a more reliable link between two machines in a datacenter.
3. A poor persistence model for long lived backups
4. No easy way to programatically recover old backups
What's even more disturbing is that this isn't a new problem. Its not like we don't know how to backup databases. This solution seems very poorly though out.