Web service
From Wikipedia, the free encyclopedia
The W3C defines a Web service[1] as a software system designed to support interoperable Machine to Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.
The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate XML messages that follow the SOAP-standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server, a description in the WSDL. The latter is not a requirement of SOAP endpoint, but it is a prerequisite for automated client-side code generation in the mainstream Java and .NET SOAP frameworks. Some industry organizations, such as the WS-I, mandate both SOAP and WSDL in their definition of a Web service.
Contents[hide] |
[edit] Specifications
[edit] Core specifications
The specifications that define Web services are intentionally modular, and as a result there is no one document that contains them all. There is also no single, stable set of specifications. There are a few "core" specifications that are supplemented by others as the circumstances and choice of technology dictate, including:
- SOAP: An XML-based, extensible message envelope format, with "bindings" to underlying protocols. The primary protocols are HTTP and HTTPS, although bindings for others, including SMTP and XMPP, have been written.
- WSDL: An XML format that allows service interfaces to be described, along with the details of their bindings to specific protocols. Typically used to generate server and client code, and for configuration.
- UDDI: A protocol for publishing and discovering metadata about Web services, to enable applications to find Web services, either at design time or runtime.
Most of these core specifications have come from W3C, including XML, SOAP, and WSDL; UDDI comes from OASIS.
See List of Web service specifications for a more complete listing.
[edit] Profiles
To improve interoperability of Web Services, the WS-I publishes profiles. A profile is a set of core specifications (SOAP, WSDL ...) in a specific version ( SOAP 1.1, UDDI 2 ...) with some additional requirements to restrict the use of the core specifications. The WS-I also publishes use cases and test tools to help deploying profile compliant Web Service.
[edit] Additional specifications, WS-*
Some specifications have been developed or are currently being developed to extend Web Services capabilities. These specifications are generally referred to as WS-*. Here is a non exhaustive list of these WS-* specifications.
- WS-Security: Defines how to use XML Encryption and XML Signature in SOAP to secure message exchanges, as an alternative or extension to using HTTPS to secure the channel.
- WS-Reliability: An OASIS standard protocol for reliable messaging between two Web services.
- WS-ReliableMessaging: A protocol for reliable messaging between two Web services, issued by Microsoft, BEA and IBM it is currently being standardized by the OASIS organization [1].
- WS-Addressing: A way of describing the address of the recipient (and sender) of a message, inside the SOAP message itself.
Some of these additional specifications have come from the W3C. There is much discussion around the organization's participation, as the general Web and the Semantic Web story appear to be at odds with much of the Web Services vision. This has surfaced most recently in February 2007, at the Web of Services for the Enterprise workshop. Some of the participants advocated a withdrawal of the W3C from further WS-* related work, and a focus on the core Web.
In contrast, OASIS has standardized many Web service extensions, including Web Services Resource Framework and WSDM.
[edit] Styles of use
Web services are a set of tools that can be used in a number of ways. The three most common styles of use are RPC, SOA and REST.
[edit] Remote Procedure Calls
RPC Web services present a distributed function (or method) call interface that is familiar to many developers. Typically, the basic unit of RPC Web services is the WSDL operation.
The first Web services tools were focused on RPC, and as a result this style is widely deployed and supported. However, it is sometimes criticised for not being loosely coupled, because it was often implemented by mapping services directly to language-specific function or method calls. Many vendors felt this approach to be a dead end, and pushed for RPC to be disallowed in the WS-I Basic Profile.
[edit] Service-oriented Architecture
Web services can also be used to implement an architecture according to Service-oriented architecture (SOA) concepts, where the basic unit of communication is a message, rather than an operation. This is often referred to as "message-oriented" services.
SOA Web services are espoused by most major software vendors and industry analysts. Unlike RPC Web services, loose coupling is more likely, because the focus is on the "contract" that WSDL provides, rather than the underlying implementation details.
[edit] Representational State Transfer
Finally, RESTful Web services attempt to emulate HTTP and similar protocols by constraining the interface to a set of well-known, standard operations (e.g., GET, PUT, DELETE). Here, the focus is on interacting with stateful resources, rather than messages or operations.
RESTful Web services can use WSDL to describe SOAP messaging over HTTP, which defines the operations, or can be implemented as an abstraction purely on top of SOAP (e.g., WS-Transfer).
[edit] Criticisms
Critics of non-RESTful Web services often complain that they are too complex [2] and biased towards large software vendors or integrators, rather than open source implementations.
There are also concerns about performance, because of Web services' use of XML as a message format and SOAP and HTTP in enveloping and transport.
[edit] Similar efforts
There are several other approaches to the set of problems that Web services attempts to address, both preceding and contemporary to it. RMI was one of many middleware systems that have seen wide deployment. More ambitious efforts like CORBA and DCOM both attempted to effect distributed objects, which Web services implementations sometimes try to mimic.
More basic efforts include XML-RPC, a precursor to SOAP that was only capable of RPC, and various forms of using HTTP without SOAP.
[edit] See also
[edit] External links
- W3C Web Services Activity home page
- Web Services Architecture (W3C Working Group Note)
- Secure, Reliable, Transacted Web Services (IBM/Microsoft white paper)
- XMethods - Collection of public Web Services
[edit] Notes
- ^ Many sources also capitalizes the second word, as in Web Services
- ^ http://www.tbray.org/ongoing/When/200x/2004/09/21/WS-Research
