Completed on 02 October 2006 by Matthias Davidek.

• Prof. Dr.-Ing. Oliver Theel
• Dipl.-Inform. Christian Storm

• Replication

Data replication is used to minimise the possibility of access failures to urgently required critical data (high access availability), but also to reduce access times to this data (load balancing). A prototype for consistent data replication was created in the department. This prototype includes a component that allows any so-called Coterie-based replication procedure to be specified. The specification of a desired special replication strategy is carried out by manually specifying an acyclic graph (in text form) or automatically by a generator. The prototype is able to process both static and dynamic replication strategies. Dynamic replication strategies are generally characterised by higher access costs on the one hand and higher access availability of the replicated document on the other. The replication strategy to be used initially is determined by the administrator at design time. In principle, the replication strategy used can be adapted to changing requirements at runtime, e.g. by adding and removing computers participating in the replication process or by changing the replication strategy. However, this requires a mechanism that recognises the need to adapt the replication strategy and is also able to identify a better replication strategy.

The task to be solved as part of the work is the design, implementation and integration of a monitoring service into the existing prototype, which monitors the computers participating in the replication process and, if necessary, triggers the adaptation of the replication strategy to new requirements. The monitoring service itself should also be designed to be highly available.

• Python
• CORBA