Data Integration

(只提供英文版本)

Big Data – Blog by YY

Data Integration

Types of Data Integration being mentioned publicly would be “Event-driven” and “Data-driven,” however, they are not the different in words definition, but also the “ action “ that triggers the syncing action.

In fact, as the emergence of Internet Of Things, people have been moving from the stage of early- adopters to the more challenging, but more profitable era of mainstream enterprise technology.

However, in this weekly post, I am gonna explain the difference between the two, instead of just  focusing on one topic, either “Event-driven” or “Data-driven.”

Event-driven integrations” mean event(s) trigger in system, then hereafter any predefined corresponding event. Events can be anything that happens in a particular system that was integrated.

Companies in industries depending on the attention and loyalty of large numbers of consumers – retailing and air travel, for examples –have already be aware of the possibilities. If you can recognize an individual customer’s mobile device moving through an airport or walk past your store, you can potentially take action to improve that customer’s experience.

For what being mentioned above, it seems “Event-driven integrations” are great in many scenario, however, it don’t allow all data to be synchronized easily and quickly. The main reasons are there are many pre-requisites processes that involves simply setting up a one event to another, which might be time-consuming and tedious to achieve a fully functional integration between business systems.

 

Data-driven integrations” mean having a different action that triggers synchronization. What means a different action is the change in the data user performed before in any systems, like new record in creation, the deletion in existed record, or even the change in an existing one. This change will cause a series of a synchronization on the target data to system(s). “Data-driven integrations” make things easy to achieve an enterprise-class type of integration due to its easy setup and maintenance.

 

There are good uses for both types of integrations. “Data-driven integrations” tend to be better for integrations with CRMs, ERPs and marketing systems where you want to keep you data in sync regardless of the event that takes place. “Event-driven integrations” are great for simple point to point data transfer when events take place in a system and you want to trigger a corresponding event in the other system.

 

That’s all about the contents on the weekly blog and hope you get the ideas on the meaning of the different types of data integrations, as well as the usage scenario.

Posted in ICG日志.