不同业务系统集成模式（摘录MSDN）

最新推荐文章于 2024-08-22 11:02:33 发布

weixin_34306446

最新推荐文章于 2024-08-22 11:02:33 发布

阅读量236

点赞数

本文介绍了三种业务系统集成模式：点对点连接确保特定消息仅被一个接收者获取；代理模式通过中间组件解耦源系统与目标系统；消息总线结合发布/订阅模式允许新应用订阅消息而不会影响现有订阅者。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

不同业务系统集成模式（摘录MSDN）<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

1．Point-to-Point Connection

Many integration projects start with the need to connect two systems, and the easiest way to do so is to use the Point-to-Point Connection pattern. A point-to-point connection ensures that only one receiver receives a particular message. For this to work, the sending system must know the location of the receiving node. The sending system often must translate the message into a format that the receiving system understands.

2．Broker

The Broker pattern and its variants are often used in both application design and integration design. The intent of a broker is to decouple source systems from target systems.

Figure 1 shows the Broker pattern and the three related patterns that refine the basic Broker pattern: Direct Broker, Indirect Broker, and Message Broker.

.NET Framework remoting is an example of Distributed Object Integration that uses Direct Broker.

Systems that use Indirect Broker do not communicate directly with each other. Instead, they communicate through a middleman—the indirect broker. The source system communicates the logical name of the target to the indirect broker. The indirect broker then looks up the target system that is registered under the logical name and passes the communication to the target system. A message broker is a specialized type of indirect broker that communicates by using messages. You can use BizTalk Server 2004/2006 as the component that implements Message Broker.

3．Message Bus and Publish/Subscribe

The advantage of a message bus is that once it is established, the cost of adding new applications is minimal. A new application can subscribe to bus messages without affecting other subscribers. Because all systems, including the new system, understand common message schemas and command messages, there is no need for additional translation.

To use a Message Bus pattern that contains a Publish/Subscribe implementation, a system sends a command message to the message bus. After the message bus receives the message, it is responsible for matching the message against a set of subscribers. The message bus then forwards the message to each of the appropriate subscribers.

Source URL:

1. Integration Patterns, MSDN, http://msdn2.microsoft.com/en-us/library/ms978718.aspx

2. Implementing Message Broker with BizTalk Server 2004, MSDN,

http://msdn2.microsoft.com/en-us/library/ms978662.aspx