DuploDB – Fast Data Sync

DuploDB is the Arket platform for bidirectional synchronisation of data between different databases, irrespective of the platform, the operating system or the geographical location.
Scroll down to find out more about its features
DuploDB establishes communication between the various applications used in the company in real time, without blocking user operations. It guarantees your company continuity and accurate consistency among all of its databases, with reduced interfacing and start up times.
Captures the change

made by the applications to data in the database

Replicates the change

in the target databases

Replicates only the change,

not the entire database

Using DuploDB, you can work with different databases and platforms both mono-directionally and bidirectionally, without making changes to the application software.

It ensures low usage of bandwidth and savings of processing activities, while guaranteeing speed of reply and constant availability of the database.

Data synchronisation using DuploDB is automatic, independent of the host IT system, geographical location or any stoppages of the program. You can apply simple and complex data transformation logics, with a guarantee of data consistency.

Interaction with databases, methods of data transfer and personalisation are optimised and you always have complete control over the status of the synchronisation through anomaly alerts and monitoring functions.

Main features of DuploDB – Fast Data Sync

Supports all the main DBMS
Supports all the main operating systems on the market
Captures and deploys data in a fully transparent manner
Simple or complex synchronisation rules
Synchronisation managed in transactional mode and self-checked
Alerts of anomalies

Who was DuploDB designed for?

The features of DuploDB, with its versatility and efficiency, provide various types of users with immediate, long-lasting benefits for their organisations or their clients. DuploDB can assist:

The IT Manager or DBA who have to quite regularly handle problems linked to data exchange, especially in companies whose locations are spread out geographically or which have not completely centralised their IT functions. DuploDB is the ideal solution also for companies with heterogeneous Software/DB architecture (departments, portals, etc.) that have to guarantee updates to their data in real time in relation to vertical application areas such as logistics, e-commerce, CRM, SFA, BI and Datawarehousing. In brief, DuploDB® is the ideal solution for companies with distributed IT systems, for example:

  • Multiple databases
  • Numerous application platforms
  • E-commerce applications
  • Same applications deployed over multiple offices/machines
  • Numerous offices with different applications

Companies that produce applications use DuploDB as a communication module between their application(s) and the architectures of their clients, eliminated the need to manage data exchange interfaces that need to be constantly modified.

In other cases, DuploDB is used by software houses which, offering a range of products that cover diversified functional areas (ERP and various departmental software), need to have a single technology that guarantees real time alignment of data among the various applications.

Software integration and development often requires dealing with complexities regarding what can be substantial differences between new technologies and the systems installed at the client. DuploDB is adopted in these cases by system integrators and developers as a facilitator, capable of significantly simplifying the problems linked to data exchange in real time.

How does DuploDB work?

The inventory of the changes made to a database is provided by the journal, a file that records the activities carried out. DuploDB® has its own journal, which intercepts all the changes at record level (insertions, changes and deletions). This information can be obtained in two separate ways, also based on the database used:

  • from the database journal
  • through Trigger, a program launched by the database that reports the changes made.

Both these methods also work when DuploDB, for any reason, is temporarily inactive (for ex., if the connection is down or due to system maintenance). As a result of this latter feature, all changes to the source database will always be recorded.

The change recorded by the DuploDB® journal is sent to all the target systems configured. Due to the bidirectional alignment, each database can both receive and send information, alternatively. Except where you decide to divide the records to be updated, all the databases will always be updated. In this phase, you can insert logics to decide whether to send a change to a certain system or transform the content in a field using functions defined in the internal scripting environment.

Before they are entered, the changes to be made are optimised, taking account of the operating methods of the target databases. Optimisation, which increases efficiency and speed, guarantees perfect communication even between systems based on different programs and languages.

The changes are inserted into the target databases. The configuration and scripting options provided by DuploDB® guarantee, in this phase as well as the others, that you can highly personalise the operations to be performed.

Thus, you can insert simple logic considerations, without having to write code, just using your mouse (e.g. synchronise this data only if the Country field is “Italy”). You can also insert highly complex logics if you need to, using javascript logic scripts or creating fields calculated through SQL queries.

DuploDB® completes its action with a checking phase, recording the outcome of the update:

  • for all positive responses, regarding updates correctly carried out, DuploDB® will notify the source database to delete the items already inserted from the journal
  • for the negative responses, DuploDB® generates one or more notification messages and autonomously manages the subsequent attempts at alignment.

This system guarantees that no data is ever lost in the synchronisation phase.

Find out the architecture and minimum requirements of the DuploDB platform

The Duplo Console is the user interface you can use to activate the licence, configure replications of tables, and check the updates and the tuning of the tables replicated. Through the user interface, you can:

  • create the instances of communication between different databases
  • define the table to replicate
  • specify the rules of data modification during the replication phase
  • control the replication process, from capturing the variation to applying it in the target table.

Task Manager is the main tool provided by the Duplo Console. It is used to configure and execute the fundamental operations of the synchronisation process on the tables configured in a specific system. You can also use Task Manager to monitor the synchronisation status, from the events processed to those pending.

Each operation of data configuration and uploading is also recorded in a log. For each system, the operation executed, time taken to execute the operation and the result of the operation are recorded. Three types of message can be recorded: informational messages on the operations executed, warning messages (they indicate that a manual operation was carried out which prevented the action from being correctly performed) and error messages.

The WebServices interface integrates with external applications that need to coordinate/control the synchronisation process.

The journal reader is the component that processes the variations captured by the triggers (or by the journal reader when the AS/400 is used) and makes them available to the sender pending events, based on the rules defined in the configuration phase. Specifically, the same transaction can be distributed over one or more target systems, with different data synchronisation and transformation rules.

The Sender Pending Events is the component of DuploDB® that takes care of sending the changes to the target system, launching as many transmission processes as there are systems to which the alignment transactions are to be sent. The principle underlying synchronisation is the possibility for a single source system to send transactions to one or more target systems, so under the header “Sender Pending Events” there will be as many entries as there are systems enabled to receive transactions from that source system.

This feature monitors in a highly detailed manner the data flows generated by DuploDB® and analyses the statistics of each synchronisation:

  • it can detect flows generated by the Journal Reader, to understand which tables have the most entries in the various source systems
  • it can conduct real time analysis of the flows sent to the various target systems
  • it can analyse bulk uploading processes

This can be highly useful in the tuning phase of the synchronisation processes, because it lets you track the recording of data flows in real time:

  • it makes the elements available to assess whether there are problems, bottlenecks or analysis/configuration anomalies to resolve
  • analyses in a detailed manner any overloads in the synchronisation processes, and consequently provides useful instructions to change the configuration of the product.
  • makes applying configuration/process optimisations more simple

Often, in fact, we do not know the methods used by the ERP procedures for processing the data, thus making it difficult to correctly assess the impact that the introduction of a system for real time data synchronisation such as DuploDB® may have.

DuploDB® works with all operating systems that support Java Virtual Machine 1.8 or later:

  • Windows Server 2012 or later
  • IBM OS400 V5R4M0 or later
  • Linux

Databases supported:

  • Microsoft SQL Server 2008 or later
  • Oracle 8.x or later
  • DB2 UDB
  • DB2/400 V5R4M0 or later
  • MySQL 5.x
  • PostgreSQL 8.0 or later
  • Firebird 3.x.x or later
  • Sybase
  • Informix
  • OpenEdge Progress

Compatible with VMware, Microsoft Hyper-V and Xen.

Want to know more about the features of DuploDB, the bidirectional data synchronisation platform?
Fill out the form to ask for more information.
Type the words you want to search...