What specific technology would you rather we use?
Just clearly abstract the storage pool layers. There are two storage pools in the Satoshi client:
A) public: blockchain and peer addresses and some settings
B) private: wallet and some settings
Any, literally any well know traditional ACID database technology would be fine. Just create the free account at Oracle's OTN and download whatever suits your fancy. If you aren't a Microsoft hater then obtain access to MSDN/Bizspark/Dreamspark/Technet and use the database technologies available there.
The things that need deep and far reaching changes in the current implementation:
1) store blockchain in a database, not in a stdio/iostream file
2) blkindex is just an index, it doesn't need full transactional logging, the lightweight metadata-only logging is sufficient
3) blkindex is just an index, if there's something wrong with it, provide a "reindex" operation, maybe as a side effect of "checkblocks/checklevel" operation
4) provide a way of obtaining sincere ledger / audit log for the transactions with multiple timestamps:
4a) true time when first seen on the p2p net
4b) true time when first seen in a block
4c) block time when seen in a block
4d) true time when some block caused a reorg and un-confirmed the transaction
4e) true time when other block reconfirmed the transaction
4f) block time when reconfirmed
4g) etc.. for each subsequent chain reorganization
The above is just a first step. The next step would be to actually integrate with any middleware:
5) get rid of "blocknotify" and support normal commit/rollback hooks supported by pretty much all distributed transactional technology, including the free Microsoft DTC.
In summary: the above isn't a "patch" or "git pull request" that can be submitted. This is a change of a mindset that would need to happen amongst the core development group. The GAAP isn't just a ruleset/certification that happens once and then you have it. It is an ongoing commitment.