What are the types of EAI Software Topology?

There are various types of EAI software topology which are as follows −

Hub/Star Topology

Hub typology helps generate a main point of control. Messages are shared from source to central hub, which is provided in the machine itself. Hub typology works if business events are autonomous and if the Message Oriented Middleware (MOM) on which the typology is based from an individual vendor. Therefore the source application shares an individual message in one format and the hub reformats the message as essential and broadcast it to the multiple radius linked to the hub.

Advantages of Hub/Star Topology

• It can be used to decrease the re-entry of the data as it is centralized.

• It can be used to promote re-use of the data.

• As all data must transform through the hub it is simple to monitor and audit data flows across the network from the hub.

• Scalability is more.

Disadvantages of Hub/Star Topology

• Mostly the hubs available cannot manage the incoming transaction from some other source than the middleware on which they work.

• They cannot handle integration events containing multiple sources and destinations.

• If database is needed, it should become a source of processing or routing bottlenecks as volumes increase and integration rules become difficult.

Bus Topology

Bus typology is beneficial for distributing data to several destinations. Source applications put messages onto a system-wide logical application bus that is accessible to different applications. One or more applications can then selectively subscribe to the messages transmitted on the bus. Traffic does not require to flow through the main switching point. This is feasible in publish and subscribing middleware only. Bus typology avoids the issues of bottlenecks.

Point-to-Point Topology

Point-to-point topology allows applications to connect directly with one another. This is beneficial when synchronous connection and persistence are needed. Applications with pre-constructed integration for ERP software use this topology.

Pipeline Topology

Pipeline topology is beneficial if the dynamic configuration is not needed and several pipelines are autonomous of each other. The data flows will be based on the First In First Out method. This is a very easy level of integration.

Network Topology

Network topology is the best option accessible if there is several asynchronous activities and autonomous transactions should coexist with one another. For this topology to work well, the interfaces should be clear and robust. If there is a difficulty at the interface level then the whole network connection can decline.