Distributed Client / Server SQLite
A Client/Server version of SQLite is still bound by the processing
capacity of a single server system. The only way to overcome this
is through the use of a cluster or cloud of server systems. The most
common approach is to use master/slave replication and forget about
ACID correctness.
Using a Group Communication System to broadcast update information
to all participating nodes seems to be a clean architecture to achieve
scalable performance and ACID correctness at the same time. Some prototype
work in Postgres showed the approach to scale to 15 nodes.
A well designed GCS is about 20,000 lines of code, about two-thirds
of the code size of the SQLite library. Using this approach has the
promise to be a radical and nimble design for a distributed database
server.
| 
