4. EXTRACT –TRANSFORM-LOAD
• First and most basic technique used to automate data transfer.
• Extract – reads data from indicated source and pulls out the relevant subset of data
(post filtering)
• Transform – works with this acquired data – using rules or lookup tables, or creating
combinations with other data – to convert it to the desired state. Surrogate keys or
new key values are applied to similar data from different source systems prevent key
collisions in the future and provide a cross reference across systems
• Load – writes the resulting data (either all of the subset or just the changes) to a
target database, which may exist or is created.
• Can be kick-started both manually and automatically, it is usually automated using
schedulers.
• ETL is ideal in situations when large volumes of data are transferred without
workflows associated with the data that is transferred – like transferring historical
data between systems.
6. • EDI came next and revolutionized how transactional data was exchanged ; it is a
communication technology used to transmit data from one system to another.
• Required data in the source system is translated into a standard EDI format using
appropriate segments and data elements depending on how the internal data is
mapped.
• Uses private data network communications network called value-added networks
(VANs) to transmit standardize transaction data between two systems.
• After translating the data into the standard format, the connection is established
with the destination system and the data is transmitted.
• The information is then extracted from the transferred data and entered into the
destination system.
• Ideal in situations where transactional data has to be exchanged between various
stakeholders on a non-real time basis.
• Communication with end applications can happen both at the database and
application API level
Point to Point – Electronic Data Interchange (EDI)
7. Point to Point – Electronic Data Interchange (EDI)
In EDI the communication with the end applications can happen both at the database and
application API level
9. • APIs are EDIs of the 21st Century
• API is a messaging format that allows data to be transmitted from one system to
another.
• With APIs, the code is simplified and structured to clearly define how a program
will interact with the rest of the applications.
• In the API based integrations, the integration application uses the APIs exposed by
both the applications to extract data from and insert data into both the systems.
Point to Point – API based Integrations
11. • Hub-and-Spoke is not very different from API based integration – hub-and-spoke
method extends the same concept but for more than two systems.
• With hub-and-spoke integration method, there are multiple applications and a
central integration application, usually hosted on the cloud, which manages the
communication between these applications.
• While the same model can be used to drive communication between just two
systems, there are some limitations that sneak in because of the architecture (as it
was designed for more than 2 systems).
• Hub-and-Spoke method is ideal in situations where you have to simultaneously
exchange information between multiple systems.
Hub-and-Spoke
12. So, what will your choice be and why?
Do get your free e-book download from – http://bit.ly/2gxbFXI
Conclusion
13. For more information
Visit : www.i95Dev.com
E-mail : info@i95Dev.com
Maryland : 3 Bethesda, Metro Center, Suite 700 Bethesda, Maryland 20814. Ph: (301) 760.7499
New York : 1430 Broadway, 7th Floor New York, NY 10018. Ph: (646) 259.3662
Texas : 5646 Milton, Suite 100, Dallas, Texas 75206. Ph: (214) 396-2121
Australia : Sydney, NSW – 2145, Ph: (02) 8015 5446
Thank You