Slightly escaping the technical language, an ESB is a software that allows you to establish communications between various business applications, allowing the reuse of functionalities and data and, thus, minimizing redundancies.
For example, if we have two or more applications making available the management features of the entity of the customers, we need to choose one to make this management available and the others whenever they need this information, send a request for this data to the selected application, and receive the response through the ESB, which serves as a communication link between applications.
In this way, we can avoid redundancies and, thus, minimize costs and increase the quality of data.
However, I must also mention that in large organizations, where there is a high flow of requests between the various applications, this can generate traffic congestion, because the ESB works centrally in the management of requests and responses.
For that reason, there are some companies that are preferring to develop their solutions based on microservices, which can work independently, case by case, avoiding congestion.
Head Of Applications Support at a comms service provider with 5,001-10,000 employees
Real User
2020-07-28T09:01:25Z
Jul 28, 2020
I would add slight thing to the nice explanation from BPMexp76
ESB would have great added value if you decided to migrate one of the core systems you use
For example if you decided to migrate Email server, instead of changing all other interfaces from all systems you have in order to integrate with new server, you only have to chabge one connection to ESB and the rest remains the same
Als nnumber of integration points would be N*(N-1) for N systems if you decided not to use ESB, but with ESB the number would be N only
A aan example if you have 10 different systems you will need 10 integration points using ESB and 90 if you don't
Enterprise Service Bus (ESB) is an architectural style that supports the integration and communication of diverse applications in real-time within an enterprise. It acts as a central hub for data information flow, enhancing flexibility and efficiency.
Designed to simplify complex application discussions, ESBs enable seamless communication by decoupling systems and reusing existing services. They offer a structured approach to integrate disparate systems, handling protocols, and conversions...
Slightly escaping the technical language, an ESB is a software that allows you to establish communications between various business applications, allowing the reuse of functionalities and data and, thus, minimizing redundancies.
For example, if we have two or more applications making available the management features of the entity of the customers, we need to choose one to make this management available and the others whenever they need this information, send a request for this data to the selected application, and receive the response through the ESB, which serves as a communication link between applications.
In this way, we can avoid redundancies and, thus, minimize costs and increase the quality of data.
However, I must also mention that in large organizations, where there is a high flow of requests between the various applications, this can generate traffic congestion, because the ESB works centrally in the management of requests and responses.
For that reason, there are some companies that are preferring to develop their solutions based on microservices, which can work independently, case by case, avoiding congestion.
@BPMexp67 thanks for a really helpful response! It seems that ESBs would then not be ideal for larger organizations - is this a correct assumption?
I would add slight thing to the nice explanation from BPMexp76
ESB would have great added value if you decided to migrate one of the core systems you use
For example if you decided to migrate Email server, instead of changing all other interfaces from all systems you have in order to integrate with new server, you only have to chabge one connection to ESB and the rest remains the same
Als nnumber of integration points would be N*(N-1) for N systems if you decided not to use ESB, but with ESB the number would be N only
A aan example if you have 10 different systems you will need 10 integration points using ESB and 90 if you don't
@Mahmoud Elkholy thanks for this!