Differences

This shows you the differences between two versions of the page.

--- tanszek:oktatas:iss_t:enterprise_service_bus_esb [2023/03/05 16:47] – létrehozva knehez
+++ tanszek:oktatas:iss_t:enterprise_service_bus_esb [2023/04/24 18:12] (current) – knehez
@@ Line 1: / Line 1: @@
 ===== Enterprise Service Bus (ESB) =====
+An Enterprise Service Bus (ESB) is a middleware architecture that provides a platform for integrating diverse applications and software components. It acts as a central hub to manage and facilitate communication between different applications and services.
+Advantages of using an ESB:
+  * is its ability to handle complex message routing and transformation between applications, which simplifies the process of integrating software components.
+  * ESBs also provide features such as security, monitoring, and logging.
+  * ESBs offer a high degree of flexibility and scalability, allowing organizations to add or remove application components as needed.
+Potential disadvantages of ESBs:
+  * One of the main drawbacks is that it can introduce additional latency to the communication process, as messages have to be routed through the ESB.
+  * Setting up an ESB can be a complex process, requiring specialized expertise and resources.
+  * ESBs can also be expensive to implement and maintain, especially for small or medium-sized businesses.
+Compared with other integration methods, such as point-to-point integration or message brokers, ESBs offer a more centralized approach to managing integrations. This can be advantageous for organizations with a large number of applications and systems to integrate. However, for smaller organizations with fewer applications, a simpler integration approach may be more appropriate.
   * The Web services are not effectively solve the interconnection of heterogeneous systems.
   * Not resolve the communication protocol deviations, i.e. during communication, the protocol offered by the service is different than the protocol used by the client.
@@ Line 5: / Line 22: @@
     * message routing – based on context and content
     * QoS (Quality of Service) – performance, security, reliability
     * data enrichment – information extension with automatic extra data
+                       +----------------------+
+                       |     Integration      |
+                       |      Repository      |
+                       +----------+-----------+
+                                  |
+                         +--------+---------+
+                         |   Enterprise     |
+                         |   Service Bus    |
+                         +--------+---------+
+                                  |
+            +---------------------+--------------------+
+            |                     |                    |
+    +-------+--------+    +-------+--------+   +-------+--------+
+    |  Application 1 |    |  Application 2 |   |  Application 3 |
+    +----------------+    +----------------+   +----------------+
+In this example, an Enterprise Service Bus (ESB) is positioned between multiple applications, represented by the boxes at the bottom of the diagram. The ESB serves as a central hub for managing the integration of these applications, and it communicates with each application using a standardized set of protocols and formats.
+An Integration Repository is a key component of an Enterprise Service Bus (ESB) architecture. It is a centralized repository that stores information related to the integration of different applications and systems.
+The Integration Repository typically contains information about the data structures, message formats, and protocols used by each application or system. This information is stored in a standardized format that is understood by the ESB, allowing the ESB to route messages and transform data between applications.
+The Integration Repository also contains other artifacts related to integration, such as mappings between different data structures, transformation rules, and message schemas.
+One of the main benefits of using an Integration Repository is that it provides a centralized location for managing the integration of multiple applications and systems.
+  * simplifies the integration process, reduce errors
+  * improve the overall efficiency of the integration process.
+  * by storing integration artifacts in a centralized location, it becomes easier to maintain and update the integration process.