First, let's take a look at the basic concepts, technical concepts, and terminologies of (Enterprise Application System) integration. Apart from the basic concepts, we will talk about the types of integration models similar to SOA, for example, point-to-point, central radiation, and pipelines, understanding the differences between EAI and EIi will also mention the future integration technology-xtp.
I. Basic Concepts
First, let's clarify some basic concepts (my own understanding ):
- A2a: integration between two applications
- B2B: integration between two business groups
- B2C: integration between business groups and end users, such as Internet Technology
- Integration type: for example, interface layer integration, data layer integration, and function layer Integration
- Semantic Integration
- EAI: Integration of data and business processes between two applications
- Message, publishing and subscription, message mediation, and message infrastructure: the concept of message-based Asynchronous integration upgrade
- ESB: an infrastructure that implements EAI and solves the decoupling problem between customer applications.
- Middleware: intermediate component for Integration
- Routing mode: some hardware routing modes such as unicast, broadcast, and multicast are used for reference.
We use a figure to illustrate the relationship between A2a, B2B, and B2C.
Ii. Integration type
After learning about a2ab2bb2c, let's see which integration types are available. In general, we can divide integration into three categories: interface integration, data integration, and function integration.
- Interface integration: it is a well-known portal. In fact, many of us integrate different applications through IFRAME.
- Data integration: shared databases, File Replication (regular synchronization), data exchange (Database Replication)
- Function integration: EAI and SOA. There are some differences between EAI and SOA as function integration methods. EAI is generally oriented towards data rather than process. EAI is usually used by a specific manufacturer's technology, therefore, knowledge of a product is required. For a long time, EAI plays a key role in solving the integration of "chimney" applications. Even if a "chimney" application provides interfaces similar to WebServices integration for integration, it cannot be regarded as an SOA architecture because SOA is process-oriented and process-driven, while EAI is usually data-driven.
Next, let's take a look at several integration methods.
- EAI (Enterprise Application Integration): The use of EAI means the unrestricted sharing of data and business processes among any connected applications (linthicum 2000 ). EAI is usually integrated in three layers: data layer, transferring files through FTP, or directly using the functions provided by the database for data replication; object level: the methods provided by objects are called by systems; process Level: relies on workflows for integration.
- Message (Queue)-based integration
Send a message through a message queue:
Publish/subscribe message consumption:
Message intermediary:
Message integration platform:
- ESB: ESB is the infrastructure for implementing EAI. Generally, it will do something like this.
Generally, ESB provides the following core functions:
The internal structure of ESB is as follows:
- Middleware integration: the middleware mentioned here is a platform for communication between applications of different technologies. Common communication methods include Session (for dialog), Request Response, message parsing, message queue, and publish/subscribe. Use the following table to compare the above methods
Middleware generally relies on relational databases, RPC, transaction-oriented, message-oriented, and component-oriented technologies.
- Routing mode: Finally, the commonly used routes are integrated. The routing mode here is inspired by the hardware and network protocols, which can be unicast, multicast, broadcast, or selected.
We will give a fresh introduction to the concepts, principles, and terms of integration. I will summarize several variants of integration and the integration mode later. If you have time, you will also briefly introduce the technologies involved in integration, the planning and integration scenarios of various layers, and the existing products (manufacturers and open source.
