In numerous workshops, the enterprise architects of many problems, such as service-oriented architecture (SOA) related issues, how to make enterprise service bus (ESB) as the backbone of building enterprise SOA framework issues. Among them, many have questioned the significance of ESB, from which also reflects the current IT group there are some common misconceptions on the ESB. The following is the author concluded that people are most concerned about the issue of 10 ESB.
Misunderstanding 1: ESB only changed names EAI
Many groups set up SOA IT architecture, while still plagued by a problem: "ESB and EAI in the end What's the difference?" ESB is used to build enterprise SOA infrastructure, EAI than the traditional agent used more widely . According to Forrester Research's report, ESB can improve connectivity, increase flexibility to promote development and strengthen the control of important resources to help companies achieve SOA value.
ESB can be used to deal with in the past not only rely on EAI tools, integration projects can also be used to establish B2B relationships between enterprises.
EAI ESB can provide can provide functionality, but the basic structure is different: the framework for the corporate shift from the traditional way of coordinating the integration of service interactions. EAI is usually applied with star structure in the form of an independent implementation.
EAI ESB functionality provided with the same agent - connectivity, application adapters, according to the rules of message routing and data transformation engine - but these features are for SOA, they distributed and deposited throughout the service bus can be deployed independently service container. This allows us to selectively deploy the required functions integrated agency, does not produce redundant. ESB container model of the distributed event-driven features to the form of on-demand services to SOA in the integrated component independent of scalability.
In order to integrate agents to support the SOA from the real and a true sense of the ESB, we 闇? to its basic function Fensan Dao Zhong component parts before it can be deployed to the various components of Duli bus and made them Xiediaoyunzuo .
We see a transformation engine based on XSLT. The XSLT engine can model the table to a kind of XML document into another XML format. I can responsibly tell you nothing more than the analysis and processing XML in the consumption of computing resources. If the application of two regular exchange between the XSLT transformation, then the conversion is likely to become a performance bottleneck and expansion. If you use the stand-alone star integrated agency approach, then to address this bottleneck and expand the deployment of this integrated agency you have to install a processing capacity of powerful machines, or installed on multiple machines - and just to solve the conversion problem. Meanwhile, the integration of other agency functions, such as routing rules for the treatment and conversion processes also rob computing resources.
And integration framework for different agents star, ESB provides a basis for the core distributed service architecture. This architecture is for the integration, it can be integrated agency in a variety of features such as message routing, data conversion, and application adapters and other selective on-demand deployment, which constitute an independent SOA-integrated service is part.
XSLT transformation can be deployed as a service to the ESB service container, and then multiple instances of this container distribution according to load balancing to many machines. If the ESB container is cross-platform, then you also have the flexibility to select the conversion services across platforms - Linux host, Solaris host, Windows host and so on. If you do not like this simple framework, it can be considered: the definition of ESB, and those who made the impugned product suppliers also provides us with convenience: You can deploy any number of lightweight ESB service container without having to pay any additional costs.
ESB to provide such integrated services can be combined with other financial services into the SOA-based processes, thereby expanding the scope of business. ESB distributed services can be combined in the line-based (itinerary-based) routing (see Errors # 7) to achieve self-oriented, message-oriented services to interact, so that all parts of ESB can work independently without on a centralized routing engine dependence.
Myth # 2: Microsoft is using "Indigo" Creating ESB
Indigo combines Microsoft Messaging Queuing, Component Object Model COM +,. NET, and Web services. They do have a Web service extension is the message bus. This enterprise service bus is very different. Message Bus exposed the details of low-level information technology, it needs to write code to define the relationship between applications and services. The ESB is about the configuration rather than coding, so do not need to hand-write the internal interoperability between various applications. ESB help to improve the form of exposure to event-driven applications on the bus between the loosely coupled characteristics. The good news is the application of Indigo to create at least a message-based, and therefore through the ESB will be relatively simple to integrate.
In other words, BizTalk Server and Indigo in some of the things that combination may be more like ESB. But there is a very important point, namely, integration of BizTalk is a star agent, it also being in front of the ESB and EAI mentioned in all the negative implications. You can not add any costs not subject to XML conversion engine to separate from the BizTalk Server load balancing services as running on multiple machines (see previous discussion of EAI and ESB).
Misunderstanding 3: WS-Rliability and WS-Reliable Messaging and other WS-* standards will eventually demand the lifting of the ESB
ESB in the design when it should be considered, and according to the continuous development of commercial applications gradually adjust the value of the standard. WS-* standards of the development of application terminals to better interact through the ESB.
The work of a variety of parallel, WS-* standards as evolving standards for Web services as part of nature there are many uncertainties. Even if these standards was to develop a robust and widely applied, they still need a platform that can offer support. ESB standards in collaboration with the bottom level of the enterprise not related to a building, layout and management of a unified model for SOA.
The implementation of WS-Reliability standard requires reliable information and store and forward processor lasting support. Enterprise messaging layer is based ESB components through the message it persistence, store and forward, message verification message protocol and with external XA-compliant transaction processor interface to ensure data transmission quality of service. ESB deployment can make the layout of complex networks transparent message routing and message through the fault-tolerant server architecture to achieve continuous availability of information facilities. In the current high-pressure business environment, to achieve all of these designs also require many years of labor.
In other words, is the deployment of proprietary messaging layer of the ESB should also, at the same time using one or more of the WS-Rel * as a supplementary agreement to prepare for that future. However, this is not a program can solve all problems, we still need a combination of a variety of information and protocols to support.
Myth # 4: model or product?
Enterprise Service Bus (ESB) The term does not actually belong to the product category; it is just an implementation and integration middleware application server coupling abstraction.
ESB is an enterprise SOA for building the backbone of the height distribution of the bus. To build a service-oriented enterprise architecture, and ESB is the foundation of this architecture bus. Since the emergence of integrated markets ESB bring a lot of impact, some integrated suppliers will release a smoke bomb that can be used in combination ESB is a middleware and application of the current facilities of the abstract model. In fact, ESB really and actually is a hardware and a few years ago can be purchased from various suppliers to. So far, manufacturing, financial services, telecommunications and retail and other industries have deployed between the number of ESB.
ESB definition should include the following basic elements:
鈼?a distributed service architecture, including an integrated component for storage of lightweight containers as a model for remote service
鈼?a can for all applications and services to provide reliable message transmission backbone of the enterprise message bus
鈼?XML Data Conversion
鈼?service orchestration and process the message content based intelligent routing
鈼?A flexible security architecture
鈼?You can configure, deploy, monitor and manage remote service management facilities
As the ESB's distributed services architecture, we can position the virtual world of any terminal to access services. The distributed services architecture is built on a service via remote configuration, deployment, management and monitoring of the lightweight service container consisting of interconnected systems. These services are achieved through a container scalability, continuous availability, low latency processing, security, consistency and quality of service (QoS) of the standardized message trunk bus to clump together.
Misunderstanding 5: ESB and J2EE application services, competition between products
ESB and J2EE app servers are highly complementary in nature. Through the use of JMS, MDB, JCA or Web services standard interfaces to connect to the ESB, even in non-J2EE environment, J2EE app server and other application servers can also be well integrated.
Most of the ESB application server technology users are also users. These users use application server and ESB as their optimal component integration environment - using the application server hosting business logic and to provide web portal in the form of services, use the ESB to integrate application servers and enterprise applications in the various back-end and data sources.
Myth 6: As long as you can use the Web service call to the portal to connect to the back-end system
Theoretically, the portal Web service call can be connected to the back-end target system, but this approach can not be extended to multiple back-end systems. Through the use of ESB, you can make the portal server via a unique interface to the bus, while the bus is a portal server may be called to the back-end systems all the various connection properties, protocol, security, and data formats of the media.
Shiyong the ESB as a gateway and portal server and may interact with the various back-end server applications of Zhongjian Cengxiangdangyu Wei Ti Gong ESB users a more flexible, Kuozhan better performance SOA, so Dang Xiangmu more successful, according to Yewuxuqiu need to change, they are free to deal with a wide range of integrated operations.
Misunderstanding 3: WS-Rliability and WS-Reliable Messaging and other WS-* standards will eventually demand the lifting of the ESB
ESB in the design when it should be considered, and according to the continuous development of commercial applications gradually adjust the value of the standard. WS-* standards of the development of application terminals to better interact through the ESB.
The work of a variety of parallel, WS-* standards as evolving standards for Web services as part of nature there are many uncertainties. Even if these standards was to develop a robust and widely applied, they still need a platform that can offer support. ESB standards in collaboration with the bottom level of the enterprise not related to a building, layout and management of a unified model for SOA.
The implementation of WS-Reliability standard requires reliable information and store and forward processor lasting support. Enterprise messaging layer is based ESB components through the message it persistence, store and forward, message verification message protocol and with external XA-compliant transaction processor interface to ensure data transmission quality of service. ESB deployment can make the layout of complex networks transparent message routing and message through the fault-tolerant server architecture to achieve continuous availability of information facilities. In the current high-pressure business environment, to achieve all of these designs also require many years of labor.
In other words, is the deployment of proprietary messaging layer of the ESB should also, at the same time using one or more of the WS-Rel * as a supplementary agreement to prepare for that future. However, this is not a program can solve all problems, we still need a combination of a variety of information and protocols to support.
Myth # 4: model or product?
Enterprise Service Bus (ESB) The term does not actually belong to the product category; it is just an implementation and integration middleware application server coupling abstraction.
ESB is an enterprise SOA for building the backbone of the height distribution of the bus. To build a service-oriented enterprise architecture, and ESB is the foundation of this architecture bus. ESB integration since the emergence of the market bring a lot of impact, some of the integration vendors will release a smoke bomb that can be used in combination ESB is a middleware and application of the current facilities of the abstract model. In fact, ESB really and actually is a hardware and a few years ago can be purchased from various suppliers to. So far, manufacturing, financial services, telecommunications and retail and other industries have deployed between the number of ESB.
ESB definition should include the following basic elements:
鈼?a distributed service architecture, including an integrated component for storage of lightweight containers as a model for remote service
鈼?a can for all applications and services to provide reliable message transmission backbone of the enterprise message bus
鈼?XML Data Conversion
鈼?service orchestration and process the message content based intelligent routing
鈼?A flexible security architecture
鈼?You can configure, deploy, monitor and manage remote service management facilities
As the ESB's distributed services architecture, we can position the virtual world of any terminal to access services. The distributed services architecture is built on a service via remote configuration, deployment, management and monitoring of the lightweight service container consisting of interconnected systems. These services are achieved through a container scalability, continuous availability, low latency processing, security, consistency and quality of service (QoS) of the standardized message trunk bus to clump together.
Misunderstanding 5: ESB and J2EE application services, competition between products
ESB and J2EE app servers are highly complementary in nature. Through the use of JMS, MDB, JCA or Web services standard interfaces to connect to the ESB, even in non-J2EE environment, J2EE app server and other application servers can also be well integrated.
Most of the ESB application server technology users are also users. These users use the application server and ESB integration of the environment as their best components - Use the application server hosting the business logic and in the form of Web portal services, application servers use the ESB to integrate with various back-end enterprise applications and data sources.
Myth 6: As long as you can use the Web service call to the portal to connect to the back-end system
Theoretically, the portal Web service call can be connected to the back-end target system, but this approach can not be extended to multiple back-end systems. Through the use of ESB, you can make the portal server via a unique interface to the bus, while the bus is a portal server may be called to the back-end systems all the various connection properties, protocol, security, and data formats of the media.
銆??浣跨敤浜咵SB浣滀负闂ㄦ埛鏈嶅姟鍣ㄥ拰鍙兘涓庨棬鎴锋湇鍔″櫒浜х敓浜や簰鐨勫悇绉嶅悗绔簲鐢ㄧ殑涓棿灞傜浉褰撲簬涓篍SB鐢ㄦ埛鎻愪緵浜嗕竴涓洿涓虹伒娲汇?鎵╁睍鎬ц兘鏇村ソ鐨凷OA锛屽洜姝ゅ綋椤圭洰鏇存垚鍔熴?鏍规嵁涓氬姟闇?眰闇?鍙戠敓鍙樺寲鏃讹紝浠栦滑涔熻兘鑷敱鍦板鐞嗗悇绉嶅悇鏍风殑闆嗘垚浣滀笟銆?br />
相关链接:
Job on the road a few lessons to remember
download flv to MP3 converter
Wong Lo Kat: Benchmarking The Danger Of
Top Audio Players
Panasonic conceal excessive Cadmium physical examination of those employees actually
Ultimate Registry operations - lock registry
FONT Tools Catalogs
J2ME Game NORMAL-FRAME
convert flv to Mov
Stamp effect in the production of Fireworks
.m4v file
Outlet, a "money map" it?
Backup And RESTORE Expert
Lists Genealogy
Matroska file
Flash visual effects of the space shuttle
No comments:
Post a Comment