Menu
Service Component Architecture: Making SOA easier

Service Component Architecture: Making SOA easier

IBM and OASIS official hails specification for transforming IT assets into reusable services, cites Web 2.0 benefits

Service Component Architecture (SCA), an SOA specification for transforming IT assets into reusable services, was hailed Tuesday as a way to build services with lower barriers to adoption and link SOA to Web 2.0.

Speaking at the OASIS Open Standards 2008 symposium in the US, IBM's Mike Edwards, co chair of the OASIS SCA Assembly Technical Committee, touted the technology. He also promoted its companion specification, Service Data Objects (SDO), which enables uniform access and manipulation of data from multiple sources, including databases and enterprise information systems. SDO and SCA are backed by companies such as IBM and SAP.

"SCA makes life simpler because it gets rid of the details of how things are accessed, where endpoints are located," said Edwards, who is a strategist in the Emerging Technologies group at IBM.

SCA provides an executable model for assembling services and supports multiple languages such as BPEL (Business Process Execution Language for Web Services), Java and PHP scripts, said Edwards.

"It's simplified because it has this principle of removing middleware APIs," said Edwards.

Web 2.0 could leverage SCA, since Web 2.0 environments are typically service environments, Edwards said. An interactive application running on a browser has pieces running on the front end that requires knowledge of connections pertaining to what is running on the front-end system and the server. SCA "is a great way to deal with that," said Edwards.

SCA offers a single programming model for aspects of the service lifecycle, including construction, assembly, and deployment. Developers can focus on writing business logic.

Also, developers are saved from having to learn more and more interfaces. "With SCA, you don't need to do that," Edwards said.

SCA is not tied to a specific programming language, protocol, technology, or runtime. It is not a workflow model such as BPEL, and it is not Web services -- although many SCA applications will use Web services, Edwards explained.

Additionally, SCA also is not an ESB (enterprise service bus). "SCA is really about the programming of applications and the ESB is the infrastructure on which those applications will run," he said.

SDO, meanwhile, gives developers a single programming model for using data sources.

Edwards cited the example of a bank using SDO and SCA for an SOA rollout. Services were built with SCA while IFX (Internal Financial Exchange) data was packaged with SDO, he said.

"Within the bank, they sold SCA as a way of enabling the business to build the services platform with very low barriers to adoption," Edwards said.

There are multiple implementations of SCO and SDO, said Edwards.


Follow Us

Join the newsletter!

Error: Please check your email address.
Show Comments