News for hackers. Stuff that matters.
Re:Deployinator: Etsy's deploy tool open sourced by swanson on Saturday July 30, 2011 @11:52PM (#2827565)
While it doesn't handle every case, using a database migration framework with Up/Down style methods as part of your deploy process can work pretty effectively.

Another option is to use a VM for your database and do a snapshot before deploying.

Re:Deployinator: Etsy's deploy tool open sourced by andrewvc on Sunday July 31, 2011 @01:25AM (#2827691)
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.

Re:Deployinator: Etsy's deploy tool open sourced by mathgladiator on Sunday July 31, 2011 @02:22AM (#2827778)
Chances 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.
Re:Deployinator: Etsy's deploy tool open sourced by nknight on Sunday July 31, 2011 @02:49AM (#2827805)
Based 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.