L3-Integrative programming and Tech

​Reasons for integration

• Technology change affects all layers; legacy does not go away so easily.

• The architecture of the organization information system depends on constraints related to the

  technology but also to the organization.

• Within an enterprise, each department may have its own IT infrastructure, systems and databases which are maintained independently. Integrating them may bring additional value to

  the company.

​

• Updating and integrating of applications is possible whenever required. New applications can be created by integrating real time data from different parts of the enterprise

​

​Reasons for integration

• Presentation integration

• Data integration and

• Function integration

​

allows the integration of new software through the existing presentations of the legacy software. This is typically used to create a new user interface but may be used to integrate with other applications.

allows the integration of software through access to the data that is

created, managed and stored by the software typically for the purposes of reusing or synchronizing data across applications.

allows the integration of software for the purpose of invoking

existing functionality from other new or existing applications. The integration is done through interfaces to the software.

LESSON 3

The challenges of integration

• Network unreliability

• Distributed systems

• Slow networks

• Heterogeneity

• Modification complexity

Integration solutions have to transport data from one computer to

another across networks.

in the worst case, every application runs on a completely separate environment, e.g., database storage is not shared among applications.

Sending data across a network is multiple orders of magnitude slower than making a local method call.

Integration solutions need to transmit information between systems that use different programming languages, operating platforms, and data formats.

each application implements its own data model. Concepts may be shared, but representation mismatches are to be expected. Mappings and transformations are required.

​

Applications change over time. An integration solution has to keep pace

with changes in the applications it connects.

LESSON 3

is an integration framework composed of a collection of technologies and services which form a middleware or "middleware framework" to enable integration of systems and

applications across organizations.

one application writes a file that another later reads. The applications need to agree on the filename and location, the format of the file, the timing of when it will be written and read, and who will delete the file.

multiple applications share the same database schema, located in a single physical database. Because there is no duplicate data storage, no data has to be transferred from one application to the other.

multiple applications share the same database schema, located in a single physical database. Because there is no duplicate data storage, no data has to be transferred from one application to the other.

one application exposes some of its functionality so that it can be accessed remotely by other applications as a remote procedure. The communication occurs real-time and synchronously.

one application publishes a message to a common message channel. Other applications can read the message from the channel at a later time.