Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Advanced CORBA programming with C++
Advanced CORBA programming with C++
Production workflow: concepts and techniques
Production workflow: concepts and techniques
Microsoft Ado.Net (Core Reference)
Microsoft Ado.Net (Core Reference)
Essential COM
Programming Php
Enterprise Service Bus
Pegboard: a framework for developing mobile applications
Proceedings of the 4th international conference on Mobile systems, applications and services
IC-service: a service-oriented approach to the development of recommendation systems
Proceedings of the 2007 ACM symposium on Applied computing
ICSOC '07 Proceedings of the 5th international conference on Service-Oriented Computing
An architecture for virtual solution composition and deployment in infrastructure clouds
VTDC '09 Proceedings of the 3rd international workshop on Virtualization technologies in distributed computing
A middleware for adaptive service orientation in pervasive computing environments
Proceedings of the 5th International Workshop on Middleware for Service Oriented Computing
Service research challenges and solutions for the future internet
Diagnosing SCA components using WOMBAT
BPM'06 Proceedings of the 4th international conference on Business Process Management
| Hi-index | 0.00 |
The service oriented paradigm is, at its core, a model of distributed software components, built around the idea of multi-protocol interoperability and standardized component contracts. The Web Services Interoperability (WS-I) profiles provide standards for runtime interoperability, and the Web Services Description Language (WSDL) and WS-Policy define service contracts that support interoperability between developer tools. A major goal of Service Oriented Architectures (SOAs) is to enable an abstraction layer that integrates and bridges over platform and implementation technology differences, effectively providing a universal business software component and integration framework. Achieving a complete solution requires a portable component model and well-defined patterns for components types. This paper examines the main requirements for a SOA programming model and identifies its most relevant characteristics. In line with SOA’s goals, such model must allow a broad community of users (including non-programmers) to create service-oriented applications by instantiating, using, assembling and customizing different component types that match the user’s goals, skills, and conceptual framework. Moreover, these component types must be portable and interoperable between multiple different vendors’ runtimes.