Explanation Of The Integration Architecture

What is the integration architecture?

In a well-designed building, electricity and plumbing generally continue to work no matter how many appliances are on. Such a building is also capable of extending without having to break the planes and start over. Why? Because it has a good architectural design.

The same applies to software systems. Software architecture is the backbone of any complex computer system. The architecture covers all the software elements, the relationships between the elements and the user interfaces with those elements. The performance and reliability of a software system depend to a large extent on the architecture of the software.

Well-designed software architecture can be extended relatively easily to accommodate new applications without requiring extensive infrastructure development.

ARCHITECTURE OF PUNTO A PUNTO INTEGRATION

The original architecture used to support the integration of systems was called point-to-point.

What are the advantages of point-to-point architecture?

Point-to-point solutions are often fast and efficient. The efficiency derived from the close linking of applications is one of the reasons why at least some point-to-point solutions will continue to be used in the foreseeable future.

What are the disadvantages of point-to-point architecture?

The downside of Point-to-Point is that, although each individual connection can be relatively simple, as the number of applications increases, so does the overall complexity of the environment. This can cause high maintenance costs and lack of flexibility when changes need to be made.

Any discussion with an integration provider will often begin with a presentation that shows the mesh of the point-to-point connections shown here.

The drawbacks do not stop there, however. All other aspects of its integrated platform will be negatively affected by the excessive use of the point-to-point option. Business Activity Monitoring (BAM), for example, is particularly difficult to develop when point-to-point connections are in use.

ARCHITECTURE OF HUB AND SPOKE INTEGRATION

By acting as a central control point, the center dealt with all message processing, including routing, division and combination of messages, mapping, etc.

Architecture of Distributed Integration

The agent's computers are connected to a single system and reduce the processing load on that system. The agents take information from the application to which they are connected, process it and send it to any target application that is interested in receiving that information. The final result is the distributed architecture

What are the advantages of distributed architecture?

Distributed architecture is governed by centralized rules and business flow requirements. Most processing is done on agent processors located near the source and destination applications. A distributed architecture can grow relatively easily. This ability to scale is a clear improvement in point-to-point and Hub and Spoke solutions.

The first attempts at distributed architecture would only work when the internal and external installations operated under the same distributed technology. The available options were:

CORBA (common object request agent architecture)

This was the open and independent architecture and infrastructure of the Object Management Group (OMG) provider that computer applications employ to work together across networks.

Microsoft COM (Common Object Model)

Java RMI enabled the creation of Java-based applications distributed to Java-based. It is now available in several software packages from Sun Systems.

What are the disadvantages of Distributed Architecture?

Many organizations have a combination of platforms and operating systems in which their business applications are executed, a situation that is often the result of mergers and acquisitions. When it is necessary to change or expand the architecture of the system, unfortunately it is not simply a question of choosing one of the distributed technologies and of implementing it. Opting for a technology can only provide a distributed solution for half of your organization due to the combination of systems that are being used.

Beyond these internal problems, there is also the issue of participating in B2B exchanges with other companies. This is another case where an eclectic mix of systems and technologies between companies can prevent the use of distributed architecture.

The providers tried to create several "bridges" between CORBA (Common Object Request Broker Architecture) and DCOM (Distributed Common Object Module) in an attempt to overcome these problems. However, these solutions never gained acceptance in the market. While the concept of a distributed environment proved promising for a long time, the business community never adopted it in large numbers.

E & I System integration Services