This sounds to me a little like making an argument for its own sake. That said, the Git data model is really elegant and interesting, and it's a good fit for ma

This sounds to me a little like making an argument for its own sake. That said, the Git data model is really elegant and interesting, and it's a good fit for many applications that need a fully versioned data store. The main issue is a single point of contention (the HEAD pointer) on every update, but if you parallelised all the update process except for that the performance would probably be ok for updates that don't otherwise conflict - certainly a good fit for a non-distributed document store. I've considered implementing the data model in something like Redis to see how it works, I think it would be pretty nice.