We use cookies to improve our website and your experience when using it. By using our services, you agree to our use of cookies. To find out more about the cookies we use and how to delete them, see our privacy policy

 

How it works

Architecture

Duplo is composed by three functional modules:

  • Variation capturing engine: buffers changes occurred, even if Duplo is inactive
  • Sender/Applier: sends the changes to target database and inserts them.
  • Management console: user interface that allows you to configure and control the entire synchronization process.

The working tools of Duplo are:

  • Task Manager: the primary tool available from user interface, it’s used to configure and perform the basic tasks of the synchronization process of the tables configured in the system.
  • Journal Reader: The journal reader is the element that processes the changes captured by the triggers and makes them available to the senders depending on the rules defined in the configuration. The same transaction can be distributed to one or more target systems, with different data transformations and synchronization rules.
  • Message log: Views the messages produced by Duplo Service Manager. Each step of configuration and data upload is recorded in this log; for each system there is a tracking of the task occurred, the time for the execution of the task and the result of the task. Three kinds of messages can be recorded:
    • Informative: messages that inform the system administrator on the tasks occurred.
    • Warning: messages requesting the attention of the administrator, as they indicate that an operation occurred which prevented the correct development of the task.
    • Error: messages that indicate a malfunction.
  • Sender pending events: The sender is the element of Duplo that sends the variations to the target system; it starts as many transmission tasks as systems to send alignment transactions. The principle is the possibility of sending, by a single source system, transactions to one or more target systems.