不同业务系统集成模式(摘录MSDN)
2007-05-01 00:36
309 查看
不同业务系统集成模式(摘录[/b]MSDN[/b])[/b][/b]
[/b]
1[/b].[/b]Point-to-Point Connection[/b]
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[/b].[/b]Broker[/b]
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.
![](http://images.cnblogs.com/cnblogs_com/rickie/BizTalk/BrokerIntegrationPattern.gif)
.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[/b].[/b]Message Bus and Publish/Subscribe[/b]
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:[/b]
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
[/b]
1[/b].[/b]Point-to-Point Connection[/b]
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[/b].[/b]Broker[/b]
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.
![](http://images.cnblogs.com/cnblogs_com/rickie/BizTalk/BrokerIntegrationPattern.gif)
.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[/b].[/b]Message Bus and Publish/Subscribe[/b]
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:[/b]
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
相关文章推荐
- IIS集成模式和经典模式 系统部署的不同
- 【unity】RPG游戏鼠标指针管理系统【单利模式】(游戏中,不同状态对于不同指针)
- IIS集成验证方式下的不同验证模式
- 走火入魔权限管理系统、插件模式集成的实现参考
- 企业信息系统集成框架(设计思路)C模式
- 业务系统如何集成工作流系统
- 用三层架构与设计模式思想部署企业级数据库业务系统开发
- 用三层架构与设计模式思想部署企业级数据库业务系统开发
- 应用集成实战系列:服务总线中的发布订阅业务模式
- 云业务系统集成服务
- 集成activiti-modeler 到 自己的业务系统(集成流程跟踪-完美支持IE)
- activiti 5.14 activitimodeler与业务系统集成(业务系统为spring,struts2,mybatis结构)
- 云计算模式和 Dell 的虚拟集成系统架构
- Atitit.biz业务系统 面向框架 面向模式---------数据映射imp
- android 系统数据业务---模式
- 减少存储过程封装业务逻辑-web开发与传统软件开发的思维模式不同
- spss C# 二次开发 学习笔记(五)——Spss系统集成模式
- (转)用三层架构与设计模式思想部署企业级数据库业务系统开发
- C#.NET 大型企业信息化系统集成快速开发平台 4.2 版本 - 几十套业务系统集中统一授权管理实现经验分享
- 【SAP业务模式】之STO(二):系统配置