What is SCA?
An essential characteristic of SOA is the ability to assemble new and existing services to create brand new application that may consist of different technologies.
Service Component Architecture defines a 'simple' service-based model for construction, assembly and deployment of network of services (existing and new ones) that is language-neutral.
SCA programming model is highly extensible. SCA can easily be extended to work with
- multiple implementation types including Java, C++, BPEL, PHP, Spring,...
- multiple bindings including Webservice, JMS, EJB, JSON RPC, ...
- multiple hosting environments such as Tomcat, Jetty, Geronimo, OSGI,..
SCA separates infrastructure concerns from business logic and enables developers to focus on business logic. It does this by defining ways to declaratively apply policy and qualities of service such as reliability, security, and transactions to service invocations.
For more information on the various SCA specifications, please visit the OSOA website.
SCA specifications have been submitted to OASIS for consideration to become standards.
Apache Tuscany implements SCA specification 1.0 in Java and C++ (referred to as Native) runtimes.
Resources
- Tuscany Overview, April 2007
- SCA Webinar and Better Webinar Slides quality
- What is SCA? A quick view of concepts through and an example walkthrough , Java Developer Journal, Article by Simon Laws, Raymond Feng, Haleh Mahbod
- The Holy Grail of services: SCA
- You can also find various white papers and articles on www.osoa.org SCA Resources about SCA.