 - Service-component architecture (SCA) is a group of specifications intended for the development of applications based on service-oriented architecture (SOA), which defines how computing entities interact to perform work for each other. Originally published in November 2005, SCA is based on the notion that all the functions in an enterprise should exist in the form of services that are combined into composites to address specific business requirements.
SCA encompasses diverse technologies, programming languages, frameworks and platforms for Web service components and for the methods used to connect them. SCA can be broken down into four major parts or models:
- The assembly model, which defines how components are combined, linked and packaged as services independent of the programming language.
- The implementation model, which defines how services are packaged and accessed for specific programming languages.
- The policy model, which defines service policies independent of the programming code.
- The bindings model, which defines how components are accessed independent of the programming code.
When properly implemented, SCA can help an enterprise to minimize the workload on its developers, shorten learning curves, facilitate reuse of services and update policies without having to modify the programming. SCA also facilitates control over access methods and the implementation of security-related countermeasures.
 |
Learn more about Service Component Architecture (SCA) |
| SCA and SDO standards: I've seen offerings from both IBM (fabric) and Tibco (Matrix) over the last few months that are leveraging this "managed container" approach for service abstraction. What are your thoughts on the SCA ... |
| Eclipse Swordfish SOA runtime mixes SCA, JBI and OSGi: For SOA development inside Eclipse, the OSGi-based Swordfish offers the potential to make the best use of Service Component Architecture (SCA) and Java Business Integration (JBI). |
| SOA standards WS-Policy, SCA and SDO advancing rapidly: Emerging SOA standard WS-Policy 1.5 is a proposed recommendation at W3C, while technical committees form to standardize SCA and SDO at OASIS. |
| ZapThink: SCA and JBI bring nothing to the SOA table: Although SCA and JBI are touted as specs for SOA, ZapThink senior analyst Jason Bloomberg argues that they will be or little of no help to the future of SOA. |
| SCA and SDO become SOA essentials for banking system: SCA and SDO, which last month began moving through the standards process at OASIS and JCP, are already being implemented in a bank processing system. |
| The top SOA/Web services stories of 2006: This two part year-in-review articles includes WS-Policy, agile development, the changing ESB and Eclipse getting more involved with SOA and Web services |
| Avoiding pitfalls of SOA application performance management: Building composite applications inside an SOA creates a new set of performance issues, requiring a deep understanding of service interdependencies. |
| Using ADO.NET and SDO for SOA data continuity: Both ADO.NET and SDO use XML to enable data transfer between disjointed components inside an SOA, enabling developers to create all kinds of new Web services mashups. |
| The concrete abstraction of the business service: Jason Bloomberg discusses implementations, interfaces, and abstractions and the many different variations of what service really means. |
| SCA and SDO for PHP: Daniel Rubio takes a look at what Service Component Architecture and Service Data Objects can offer PHP applications. |
| LAST UPDATED: |
05 Jul 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
