From DCI to presenters, from Uncle Bob's architecture talk and Avdi Grimm's upcoming 'Objects on Rails' book to the proliferation of (competing? complementing?) database systems, it seems the time has come to seriously consider decoupling our objects' persistence from the rest of the application.
This talk -- after describing the general vices of strong object/database coupling and the all-too-usual rails g model-driven development -- covers the various approaches to separating the objects' persistence layer, along with their virtues (cleaner, simpler tests! backend independence! no RDBMS-related shortcuts impacting the design!) and potential vices (performance? perceived compexity? YAGNI?).