In this post I will explain what is SOA, why SOA is required for next IT generation ,these are the questions comes to you when you learn SOA.
A service-oriented architecture (SOA) is a combination of consumers and services that collaborate, is supported by a managed set of capabilities is guided by principles, and is governed by supporting standards.
Consumers and services are all participants and collaborators in an SOA. Which is they interact with one another to request services and resolve these requests. The context for these interaction is determined by the service interface and is typically expressed as a message that moves between the collaborators.
In Service-oriented architecture consumer is technology that in some manner interacts with, consumes, and exploits services. Typically and within the definition of an SOA, a consumer is an application or piece of software that will interact with another application or piece of software as a service or possibly as an intermediary. While SOA consumers are generally software, this is changing, and we'll begin to see more appliance and hardware SOA consumers.
From an SOA perspective the service is generally some set of application functionality. The provider of the service may be a combination of the service behavior and the location at which it is identified and invoked. Again using the office supply analogy, the service being offered is that of returning the available inventory for an item. In this regard, the office supply store is know as the service provider. The interaction between the consumer and the service is enabled by a request for the available inventory position of an item and the inventory count returned in the reply.
In Service-Oriented Architecture interesting extension of the consumer and service definition is that of an intermediary. As implied by the name, an intermediary is positioned somewhere between a consumer and a service. Note that this is logical positioning, and the physical or network locations of the consumers, services and intermediaries can vary. An intermediary may provide some form of service behavior, or it may just mediate between other consumer and services. If we carried our office supply analogy further, an example of an intermediary might be a discount retailer. The customer interacts directly with the discount retailer, and the retailer then works with the office supply company on behalf of the consumer.
In service oriented architecture a consumer interacts with an intermediary rather than directly with the service. Depending upon the perspective and direction of the interaction, an intermediary can hold similar roles of both a consumer and a service when following the interaction from the consumer to the intermediary, the intermediary can be thought of as the target of the interaction or even as logical extension of the service. When following the interaction from the intermediary to the service, the intermediary can be thought of as an originator of the request or logically as a consumer of the service.
This front end such as mediation service, wrapper service might be another separate application that does nothing but mediate the interaction between consumers and the existing application. In this mediation service acts as an intermediary between service consumers and the legacy application.
One every important point to remember is that with any interaction the service interface is a critical component. It describes the rules by which the SOA participants and collaborators interact, and it also defines the context of that interaction as one or more messages.
A service-oriented architecture (SOA) is a combination of consumers and services that collaborate, is supported by a managed set of capabilities is guided by principles, and is governed by supporting standards.
Consumers and services are all participants and collaborators in an SOA. Which is they interact with one another to request services and resolve these requests. The context for these interaction is determined by the service interface and is typically expressed as a message that moves between the collaborators.
In Service-oriented architecture consumer is technology that in some manner interacts with, consumes, and exploits services. Typically and within the definition of an SOA, a consumer is an application or piece of software that will interact with another application or piece of software as a service or possibly as an intermediary. While SOA consumers are generally software, this is changing, and we'll begin to see more appliance and hardware SOA consumers.
SOA Consumer and Service
From an SOA perspective the service is generally some set of application functionality. The provider of the service may be a combination of the service behavior and the location at which it is identified and invoked. Again using the office supply analogy, the service being offered is that of returning the available inventory for an item. In this regard, the office supply store is know as the service provider. The interaction between the consumer and the service is enabled by a request for the available inventory position of an item and the inventory count returned in the reply.
In Service-Oriented Architecture interesting extension of the consumer and service definition is that of an intermediary. As implied by the name, an intermediary is positioned somewhere between a consumer and a service. Note that this is logical positioning, and the physical or network locations of the consumers, services and intermediaries can vary. An intermediary may provide some form of service behavior, or it may just mediate between other consumer and services. If we carried our office supply analogy further, an example of an intermediary might be a discount retailer. The customer interacts directly with the discount retailer, and the retailer then works with the office supply company on behalf of the consumer.
In service oriented architecture a consumer interacts with an intermediary rather than directly with the service. Depending upon the perspective and direction of the interaction, an intermediary can hold similar roles of both a consumer and a service when following the interaction from the consumer to the intermediary, the intermediary can be thought of as the target of the interaction or even as logical extension of the service. When following the interaction from the intermediary to the service, the intermediary can be thought of as an originator of the request or logically as a consumer of the service.
This front end such as mediation service, wrapper service might be another separate application that does nothing but mediate the interaction between consumers and the existing application. In this mediation service acts as an intermediary between service consumers and the legacy application.
One every important point to remember is that with any interaction the service interface is a critical component. It describes the rules by which the SOA participants and collaborators interact, and it also defines the context of that interaction as one or more messages.
No comments:
Post a Comment