👉 What is point-to-point integration?
* This is simple way of integration among the integration models. This integration model is used when the sender sends a message and it is received only by one receiver. (1 sender : 1 receiver).
* Example : Updating the human resource database with the information from an ERP system.
* This means the IP addresses all the system/services should be stored in each individual system/service in the organization for an effective communication.
* The number links in the overall integration is equal to
Number of Links = N ( N - 1 )
👉 What are the advantages in point-to-point integration?
* This integration provides a way to connect between all systems/services throughout the organization.
👉 What are the drawbacks of point-to-point integration?
* Complexity due to the number of physical links which in turn hardens to find errors when there is a fault.
* The main drawback is the difficulty in update of the services.
Lets consider a scenario where the IP address of a particular system/service changes in an instance. Now each and every system/service should be re-configured to set the newly added IP address. This can yield more time and it is cost consuming.
👉 What is the solution for the drawback in point-to-point integration?
* The main idea behind the drawback is that its tight coupling between the services or the systems. Since the IP address and necessary configurations are fed into each system/service individually, the problem arises.
* `This can be prevented by using the mediator design pattern in the integration model.
👉 What is used as the mediator in the above scenario?
* The ESB or the service proxy is used as the mediator in this scenario.
* Now the ESB/service proxy serving as the mediator the messages flow only across the necessary sender and the receiver.
* All the system/services configurations in the organization are configured in the service proxy, not in the individual systems.
* This serves as the solution for updating the configuration in one system/service.
* In case the configuration of the system/service changes it is only needed to change the configuration in the service proxy not on all individual components.
* This helps in creating, updating and deleting the components in the enterprise environment.
* The complexity of he communication is also decreased and helps to easily understand the flow of the communication path.
👉 What is an ESB?
* Enterprise Service Bus (ESB) is a software architecture model used for designing and implementing the interaction and communication between mutually interacting software components in service oriented architecture.
* An example for ESB is the WSO2 ESB.
👉 What are the features of ESB?
* Promotes asynchronous message passing between the components.
* Identify the type of message and route in-between the receivers.
* Allow message to transport across different transport protocols.
* System status, statistics with graphs are maintained. -- More of WSO2 ESB feature --
* SOAP tracer.
* Logs, configuring and monitoring.
* Allow secure and reliable communication.
👉 What are the architecture of WSO2 ESB?
* The above diagram shows the arrangement of WSO2 ESB.
* The ESB is totally dependent on the WSO2 Carbon.
* The WSO2 ESB mainly consists of WSO2 Carbon and the Apache Synapse.
* The WSO2 ESB lies above the Apache Tomcat Server,
* The Apache synapse is based on Axis2 or Java.
* This acts as an Apache mediation library for different protocols.
* Supports different protocols through SOAP based proxy services.
👉 Instance of using ESB in a business scenario?
* Consider a business scenario where the user has to download an image from the drop box, post it to Facebook and send notifications to his/her friends in twitter.
* In this kind of complex scenario a ESB can be used.
* The user can get the image in drop box through request in ESB .
* Then the ESB can handle the posting to Facebook then sending notifications to friends in twitter,
* Finally the user is notified from the ESB that the process is successful.
No comments:
Post a Comment