Service-Oriented Architecture (SOA)


(n.) Abbreviated SOA, Service-Oriented Architecture is an application architecture in which all functions, or services, are defined using a description language and have invokable interfaces that are called to perform business processes. Each interaction is independent of each and every other interaction and the interconnect protocols of the communicating devices (i.e., the infrastructure components that determine the communication system do not affect the interfaces).
SOA Benefits and Disadvantages

SOA provides a strategic capability for integrating business processes, data, and organizational knowledge. Because interfaces are platform-independent, a client from any device using any operating system in any language can use the service. In a service-oriented architecture, clients consume services, rather than invoking discreet method calls directly. There are many benefits of SOA, including improved information flow, location transparency, internal software organization and better data translation. The most commonly discussed disadvantage of SOA is for applications with GUI functionality. These types of applications become more complex when using SOA.
SOA is Not Web Services

Although it is built on similar principles, SOA is not the same as Web services, which indicates a collection of technologies, such as SOAP and XML. Web services can be thought of as a consumer-provider relationship on the Web while SOA is about designing your architecture to best work in a Web service environment. It is more than a set of technologies and runs independent of any specific technologies.

Read Also:

  • SOBA

    Short for Service Oriented Business Applications, SOBA represents the expected end state of the Service-Oriented Architecture (SOA) vision. That is, SOBAs are business applications that function in a service-oriented environment to provide discrete units of business-level functionality through well-defined service contracts (keeping the services encapsulated and self-contained). Within the SOA model these services can be […]

  • SOMA

    Short for Service Oriented Modeling and Architecture, it refers to the more general domain of service modeling necessary to design and create a Service-Oriented Architecture. SOMA covers a broader scope and implements service oriented analysis and design through the identification, specification and realization of services, components and flows. [Source: Skyway SOA Platform]

  • SharePoint Records Management

    The Records Management infrastructure of Microsoft Office SharePoint Server (MOSS) is designed to archive information no longer necessary in the daily running of the enterprise. The component is designed to ensure and protect the integrity of the content, register changes and authorization, ensure saved information is accessible only to authorized personal, and, most importantly, ensure […]

  • SharePoint Solution Packages

    SharePoint Solution Package files are Microsoft’s “preferred choice” for deploying Windows SharePoint Server (WSS) components. A Solution Package is a single compressed Windows Solution Package (.wsp) file containing all the necessary resources. A .wsp file can contain one or more WSS components.

  • SheerVideo

    A family of fast, lossless QuickTime and AVI codecs developed by BitJazz, SheerVideo is a production-based codec that is popular because of its support of Y’CbCr 4:4:4 and 4:2:2 formats, for both 10-bit and 8-bit channels, and for both progressive and interlaced data. It is also available for both Mac and PC for cross platform […]


Disclaimer: Service-Oriented Architecture (SOA) definition / meaning should not be considered complete, up to date, and is not intended to be used in place of a visit, consultation, or advice of a legal, medical, or any other professional. All content on this website is for informational purposes only.