A lot of times, the changed record can only be loaded to the destination, as it is.
Many replication tools are providing very basic data transformations capabilities.
The lack of ability to perform complex transformation on your data, results in having two layers i.e., replication and integration.
With this comes the need to manage two different set of tools catering to these two layers..
Ability to do bi-directional replication
Lastly, there is always a need, especially in a Data Hub Architecture, to have a bi-directional replication.
Let us take the same example of a manufacturing company. Once the data changes from legacy system is updated on Salesforce, the process now should take the Salesforce Id, and update the legacy database back as an acknowledgment.
Ability of the tool to be able to perform such bi-directional replication comes then becomes essential..
Stambia Component for CDC simplifies the setting up of a CDC process and lets you utilize all the integration features that come with it, as a data integration tool.
The same solution packed with the CDC templates can fulfill the requirement, therefore, there is no downtime..
Key Features of the CDC Component
Detection of the Modification
Stambia being an E-LT tool, relies on the source database CDC capabilities.
A lot of database technologies now offer in-built APIs or processes that can be used to avoid any overhead on the source system.
As an example, PostgreSQL provides Write Ahead Logs (WAL) that can be used for data replication and subscribers can be set-up for it.
With the same agility as the other Stambia components, the Change Data Capture component is directly usable and offers a high level of productivity due to the model driven approach of Stambia and the use of native "transactional or redo log" files of databases or the use of simple triggers.