3 ms·
Well, yeah, but if you perform financial transactions, you can't just lose 5 minutes of history. Also, for a DB, LVM's probably just as good as a full VM.
by andrewvc 15y ago
Well, yeah, but if you perform financial transactions, you can't just lose 5 minutes of history.
Also, for a DB, LVM's probably just as good as a full VM.
- mathgladiator 15y agoChances are good that important tables do do transactions don't change as often as other things in the system. This is why I support things like CouchDB to handle the non-transaction stuff.
- nknight 15y agoBased on a very brief conversation I had with a Paypal engineer a few years back, it's SOP in modern financial transaction handling to store/log details of every transaction in many places and various forms, and there's plenty of (probably excessive) paranoia involved. The context of the discussion was performance, scalability, and engineering resources, so we didn't get into how the logs are used, but it would be my guess that if the "primary" database had some sort of failure that lead to a rollback, affected accounts would be locked out until the transactions can be properly recovered from other storage/logging mechanisms.