Skip to content
albanmartel edited this page May 7, 2014 · 1 revision

10 Storage (DB)

Architecture

All writing operations are done through SQL transactions. Each query of the transaction must concern only one record. (only simple REPLACE or DELETE statements are allowed). The transaction handler can automatically detect which object is written by the query and then, if necessary, can run the main shared environment synchronization (call of the specialized Load static method) and then the Inter-SYNTHESE synchronization.

Comments :

  • The storage into the database is compulsory
  • The storage into the shared environment depends on the implementation of the table synchronizer
  • The synchronization through Inter-SYNTHESE is available on each table, and in done according to rules defined in the InterSyntheseSlaveSimulator

Storage in the database

The storage in the database is done by 10x modules, using the standard API of the chosen DBMS.

Synchronization of the main shared environment.

The main environment is synchronized by the Load method, defined by each table sync class :

  • a new object is created, stored in the registry, loaded, and then linked to other objects of the environment, if necessary.
  • an updated object is unlinked, reloaded, and then linked to other objects of the environment.
  • a deleted object is unlinked, ant then removed from the registry

Inter-SYNTHESE synchronization

See a tool to simulate slaves : InterSyntheseSlaveSimulator

Clone this wiki locally