Difference between revisions of "Service Component Architecture (SCA)"
(Created page with "'''Service Component Architecture (SCA)''' is a set of specifications which describe a model for building applications and systems using a Service Oriented Architecture (SOA...") |
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).) |
||
| Line 1: | Line 1: | ||
| − | '''Service Component Architecture (SCA)''' is a set of specifications which describe a model for building applications and systems using a [[Service Oriented Architecture (SOA)]]. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services. SCA is based on the idea that business function is provided as a series of services, which are assembled together to create solutions that serve a particular business need. These composite applications can contain both new services created specifically for the application and also business function from existing systems and applications, reused as part of the composition. SCA provides a model both for the composition of services and for the creation of service components, including the reuse of existing application function within SCA compositions. SCA aims to encompass a wide range of technologies for service components and for the [[Access Method|access methods]] which are used to connect them. For components, this includes not only different [[Programming Language|programming languages]], but also [[Framework|frameworks]] and environments commonly used with those languages. For access methods, SCA compositions allow for the use of various communication and service access technologies that are in common use, including, for example, Web services, messaging systems and [[Remote Procedure Call (RPC)]].<ref>Definition - What is Service Component Architecture (SCA)? [http://www.oasis-opencsa.org/sca Oasis]</ref> | + | '''[[Service]] Component [[Architecture]] (SCA)''' is a set of specifications which describe a [[model]] for building applications and systems using a [[Service Oriented Architecture (SOA)]]. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services. SCA is based on the idea that [[business]] function is provided as a series of services, which are assembled together to create solutions that serve a particular business need. These composite applications can contain both new services created specifically for the [[application]] and also business function from existing systems and applications, reused as part of the composition. SCA provides a model both for the composition of services and for the creation of service components, including the reuse of existing application function within SCA compositions. SCA aims to encompass a wide range of technologies for service components and for the [[Access Method|access methods]] which are used to connect them. For components, this includes not only different [[Programming Language|programming languages]], but also [[Framework|frameworks]] and environments commonly used with those languages. For access methods, SCA compositions allow for the use of various communication and service access technologies that are in common use, including, for example, Web services, messaging systems and [[Remote Procedure Call (RPC)]].<ref>Definition - What is Service Component Architecture (SCA)? [http://www.oasis-opencsa.org/sca Oasis]</ref> |
Latest revision as of 18:17, 6 February 2021
Service Component Architecture (SCA) is a set of specifications which describe a model for building applications and systems using a Service Oriented Architecture (SOA). SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services. SCA is based on the idea that business function is provided as a series of services, which are assembled together to create solutions that serve a particular business need. These composite applications can contain both new services created specifically for the application and also business function from existing systems and applications, reused as part of the composition. SCA provides a model both for the composition of services and for the creation of service components, including the reuse of existing application function within SCA compositions. SCA aims to encompass a wide range of technologies for service components and for the access methods which are used to connect them. For components, this includes not only different programming languages, but also frameworks and environments commonly used with those languages. For access methods, SCA compositions allow for the use of various communication and service access technologies that are in common use, including, for example, Web services, messaging systems and Remote Procedure Call (RPC).[1]