> Is there a standard strategy for optimizing balance queries against a series of transactions?

Nope!

But it's not terribly hard to design something.

I demote the DB down to a caching layer, and promote the ledger as the source of truth. All writes are appended to the ledger. Something listens to the ledger and updates the DB. Reads are against the DB.