I haven't read the full paper yet. But this sounds like a winner to me. It's actually not a database, but a transaction scheduling system sitting in front of the databases.

Hopefully these sort of ideas make it into Postgres for scalability.