It may. The real question in my opinion is: What kind of replication we need? We want to replicate just to being sure that the data is safe? Then really you co

It may. The real question in my opinion is: What kind of replication we need? We want to replicate just to being sure that the data is safe? Then really you could simply stream to all the replicas what happens to the master. You want to increase read performance? Then you first start caching result, then you start stream to slave and only make read from them. You want to increase write performace? That is quite a bad beast. You start by making the single instance as fast as possible (96k insert per second [1]) then you pretty much hit the ceiling in my opinion. You could partition the SQL tables, but then what happens to joins and select? They must go over the network (high latency), spot distributed deadlock (highly variable latency) and it start to become an huge complex project. [1]: http://stackoverflow.com/questions/1711631/improve-insert-per-second-performance-of-sqlite http://stackoverflow.com/questions/1711631/improve-insert-pe...