Service Component Architecture
Links
What every architect should now know about the Service Component Architecture (SCA)Johan den Haan: The definition of ‘application' is rapidly changing. As the industry is moving from using an application-centric architecture to a Service Oriented Architecture (SOA), the focus for building functionality is moving to Service Oriented Business Applications (SOBA). This means that applications are a set of services and components working together in fulfilling a certain business need. The technology, specifications, and standards for specifying these components and services may vary, and most often religious discussions are going on about the usefulness of each of them.- Service Component Architecture - |
|
B Margolis (2007)
Service-Oriented Architecture (SOA) is a way of organizing software. If your company’s development projects adhere to the principles of SOA, the outcome will be an inventory of modular units called "services," which allow for a quick response to change. This book tells the SOA story in a simple, straightforward manner that will help you understand not only the buzzwords and benefits, but also the technologies that underlie SOA: XML, WSDL, SOAP, XPath, BPEL, SCA, and SDO. And through it all, the authors provide business examples and illustrations, giving a practical meaning to abstract ideas.
|
|
SCA V1.0 Publication and OASIS Standardization Intent Announcementhttp://osoa.org/pages/viewpage.action?pageId=4178 Open SOA Collaboration Chooses OASIS to Advance SCA and SDO Specifications. March 21, 2007 - Eighteen leading technology vendors focused on driving technology initiatives supporting the creation of industry standards around service oriented architectures (SOA), today announced that key Service Component Architecture (SCA) and Service Data Objects (SDO) specifications have completed incubation and will be formally submitted to OASIS for advancement through its open standards process. The SCA specifications are designed to help simplify the creation and composition of services, critical to building applications using services based on an SOA approach. With these SCA specifications now mature, the partners intend to turn over their standardization process to OASIS. Additionally, the partners have completed work on the SDO specifications, designed to enable uniform access to data residing in multiple locations and formats, and will turn over stewardship of SDO/Java work to the Java Community Process and non-Java (C++) work to OASIS.- Service Component Architecture - Service-Oriented Architecture - |
|
Open SOA CollaborationThe Open SOA Collaboration represents an informal alliance of industry leaders that share a common interest: defining a language-neutral programming model that meets the needs of enterprise developers who are developing software that exploits Service Oriented Architecture characteristics and benefits. The Collaboration is not a Standards Body; it is an alliance who wish to innovate rapidly in the development of this programming model and to deliver Specifications to the community for implementation. These specifications are made available to the community on a Royalty Free basis for the creation of compatible implementations. When mature, the intent is to hand these specifications over to a suitable Standards Body for future shepherding. The Open Service Oriented Architecture collaboration is currently working on a series of specifications that are made available to the industry on a Royalty Free licensing basis. This site is the focal point both for completed specifications, and for early draft specifications where we seek community feedback. The Industry Partners are currently working on two main projects: Service Component Architecture (SCA) and Service Data Objects (SDO). Service Component Architecture aims to provide a model for the creation of service components in a wide range of languages and a model for assembling service components into a business solution - activities which are at the heart of building applications using a service-oriented architecture. Service Data Objects aims to provide consistent means of handling data within applications, whatever its source or format may be. SDO provides a way of unifying data handling for databases and for services. SDO also has mechanisms for the handling of data while detached from its source.- Service Component Architecture - Service-Oriented Architecture - |
|
