REKO

REKO. REKO is a data replication software between databases . It was designed and fully implemented using Open Source tools and free licensed class libraries. It is being used in the Venezuelan Penitentiary Management System ( SIGEP ), installed in 21 servers and in the DALASQ Flow Management System . It has been adopted as a replica solution in the Government Management System , Crime Prevention , Cuban ERP and Alas-HIS . It has been registered as a product and has been released by CALISOFTtwice. REKO constitutes a high-impact sovereign solution in import substitution since it is a mature solution built on an architecture in modern and free technologies.

Summary

[ hide ]

  • 1 Emergence
  • 2 Features
  • 3 Main components
  • 4 Main functionalities
  • 5 Application in projects
  • 6 Sources

Emergence

REKO arises from the need that arose in the distribution of data on Oracle 10g in the Venezuelan Penitentiary Management System (SIGEP) in 2007 . After analyzing the existing solutions in the world of free software and analyzing the costs of commercial solutions, the decision was made to dedicate effort to developing its own solution since there were no free software solutions that met the needs and the proprietary ones represented high expensive due to the high number of centers involved.

The first version of REKO was released by CALISOFT in 2008 to be deployed in SIGEP, but as other projects within the University of Computer Science began to use it with new requirements, new functionalities were added, such as the configuration and solution replication conflicts and scheduled replication settings. In 2010REKO was finally registered as marketable software, owned by the then Center for Technology Consulting and Systems Integration, and a second version of the software was also released in that year, with added functionalities. Currently, REKO constitutes mature software and a robust solution to a high set of replication scenarios for which it has been tested, and also has a development community at the University of Computer Sciences that supports it.

characteristics

REKO has been implemented on the Java Enterpise Edition (JEE) platform that provides a robust architecture for the development of business applications in the Java language using a multilayer model and includes a series of APIs (Application Programming Interface), technologies, development tools and specifications and reference implementations of the services provided by the platform.

Spring was also used , a lightweight container and framework , based on dependency injection and aspect orientation.

It aims to cover the main needs related to the distribution of data among the most popular managers such as protection, recovery, data synchronization, data transfer between different locations or the centralization of information in a single location. It has been designed to allow the replication and synchronization of data online and offline, the selection of data to be replicated and the definition of replication filters, it replicates data between databases with heterogeneous structures, and between heterogeneous managers.

Main components

  • Core: It handles the fundamental configurations of the software and groups the main information processing functionalities.
  • Change Capture: It captures the changes that are made on the DB and delivers them to the Change Distributor.
  • Change Applicator: It executes on the DB the changes that are replicated to the DB.
  • Change Distributor: Determines where each change made in the DB should be sent, sends them and is responsible for ensuring that each change reaches its destination.
  • Replica Local DB: It is used to save the replica’s own configurations, the actions on the DB that have caused conflict when applied, and the actions or transactions that have not been able to reach their destination.
  • Administration Web Console: Represents the software interface. It allows to carry out the main software configurations such as the node registration, configuration of the tables to be replicated, data to be replicated and the monitoring of the software operation.
  • JMS Server: Messaging Server under the Java Message Service specification, it is used as an intermediate point in the distribution of the information sent under JMS.
  • FTP server: The FTPserver is used optionally in the operation of the software. The main function of using an FTP server is to send large replica files and to be able to resume transmission in case of connection problems.
  • Database: It is the database that is being replicated, the replication software sends the changes that are made to it and applies the changes that come from other replica nodes.

Main functionalities

  • Support for data replication in online and offline environments:
  • Support for replication between databases with different structures.
  • Support for replication of external files in the database.
  • Support for data synchronization in online and offline environments.
  • Filter-adjusted selection of replication data.
  • Support for data replication between different managers ( PostgreSQL– Oracle ).
  • Support for automatic and manual conflict resolution.
  • Real-time monitoring of replica data.
  • Large data replication with summarization capabilities.
  • Ability to create and adjust to complex replication scenarios.
  • Replica management interface.
  • Support for scheduling the moment to capture and send replica data.

Application in projects

  • Venezuelan Penitentiary Management System (SIGEP).
  • DALASQ Flow Management System.
  • Government Management System.
  • Crime Prevention.
  • Wings-HIS

 

Leave a Comment

Scroll to Top