Integrations and Pathways
In each integration project systems are linked to each other for the exchange of data or to trigger an action. For example, for the processing of online-shop orders a connection to the ERP system is often necessary, which in turn generates an invoice. Instead of speaking of “shop/ERP integration” and anticipating this in the project plan we differentiate at a more granular level. This is because there is further data in other application scenarios which is exchanged by both systems (customer data, item master data, prices, stock levels, reservations, cancellations & returns etc.). E2E BRIDGE differentiates therefore between integration paths within a single integration project.
|Shop/ERP||SE1||Shop||ERP||Oder||on-demand / REST call||synchronous-asynchronous||n||2|
|Shop/ERP||SE2||ERP||Shop||Item||täglich / batch||asynchronous-asynchronous||n||1|
|Shop/ERP||SE3||ERP||Shop||Stock||on-demand / REST call||synchronous-synchronous||y||aktive / refresh every 5 Min.||1|
This method of distribution enables users to prioritize their integration projects in a finely granular way and in the same way to implement, test, deploy and control them in a detail based way. Each path can be implemented and rolled out as an individual service (see Agile Architecture).