Playing at the Cutting Edge: Service Oriented Architecture
Service-Oriented Architecture (SOA expresses a perspective of software architecture that defines the use of services to support the requirements of software users.
In an SOA environment, resources on a network are made available as independent services that can be accessed without knowledge of their underlying platform implementation
Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.
Service Oriented Architecture was first proposed by Roy W. Schulte and Yefim V. Natis who are Gartner analysts. They specified SOA as "a style of multi-tier computing that helps organizations share logic and data among multiple applications and usage modes."
SOA is usually based on Web services standards (e.g., using SOAP or REST) that have gained broad industry acceptance. These standards (also referred to as Web service specifications) also provide greater interoperability and some protection from lock-in to proprietary vendor software. However, one can implement SOA using any service-based technology.
SOA can also be regarded as a style of Information Systems architecture that enables the creation of applications that are built by combining loosely coupled and interoperable services[citation needed]. These services inter-operate based on a formal definition (or contract, e.g., WSDL) which is independent of the underlying platform and programming language. The interface definition hides the implementation of the language-specific service. SOA-compliant systems can therefore be independent of development technologies and platforms (such as Java, .NET etc). For example, services written in C# running on .Net platforms and services written in Java running on JEE platforms can both be consumed by a common composite application. In addition, applications running on either platform can consume services running on the other as Web services, which facilitates reuse.
Financial Industry Floats Open-Source Messaging Standard for Web Services, SOA
Service Oriented Architecture: SOA, BPEL, and JBI
Implementing Service-Oriented Architectures (SOA) with the Java EE 5 SDK This article presents concepts and language constructs necessary to developing a SOA composite application in Java EE 5 and describes an example application based on a loan application use case.
Sun looks to boost Java-.Net interoperability BT cuts costs with service-oriented architecture
In an SOA environment, resources on a network are made available as independent services that can be accessed without knowledge of their underlying platform implementation
Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.
Service Oriented Architecture was first proposed by Roy W. Schulte and Yefim V. Natis who are Gartner analysts. They specified SOA as "a style of multi-tier computing that helps organizations share logic and data among multiple applications and usage modes."
SOA is usually based on Web services standards (e.g., using SOAP or REST) that have gained broad industry acceptance. These standards (also referred to as Web service specifications) also provide greater interoperability and some protection from lock-in to proprietary vendor software. However, one can implement SOA using any service-based technology.
SOA can also be regarded as a style of Information Systems architecture that enables the creation of applications that are built by combining loosely coupled and interoperable services[citation needed]. These services inter-operate based on a formal definition (or contract, e.g., WSDL) which is independent of the underlying platform and programming language. The interface definition hides the implementation of the language-specific service. SOA-compliant systems can therefore be independent of development technologies and platforms (such as Java, .NET etc). For example, services written in C# running on .Net platforms and services written in Java running on JEE platforms can both be consumed by a common composite application. In addition, applications running on either platform can consume services running on the other as Web services, which facilitates reuse.
Financial Industry Floats Open-Source Messaging Standard for Web Services, SOA
Service Oriented Architecture: SOA, BPEL, and JBI
Implementing Service-Oriented Architectures (SOA) with the Java EE 5 SDK This article presents concepts and language constructs necessary to developing a SOA composite application in Java EE 5 and describes an example application based on a loan application use case.
Sun looks to boost Java-.Net interoperability BT cuts costs with service-oriented architecture
0 Comments:
Post a Comment
<< Home