This can be overcome by utilizing a transaction layer with fundamentally different authority and rollback than implemented in the major commercial offerings. Such a layer can be implemented completely above the database layer. Traditional methods of maintaining the authority of a database require master records to be located on a single server for update operations where full classical transaction support is required. This allows creation of a single serialized value history for supporting rollback and commit operations. Such a requirement for a single transactional server at the instant of transaction limits transacting databases to a single master with zero or more slave systems, introducing significant latency in completing a lock and update cycle when attempting to clear transactions in multiple geographically disparate locations.
Nodes now become authoritative for only events that origionated at the node.
State tables are now within a controllable time interval of current at all locations, but never exactly accurate in general. Copyright 1999-2001 Open Source Development Network. All rights reserved.