Recommended Free Tools
Web services protocols and related standards define how software services exchange messages, describe interfaces and, sometimes, help clients discover services. SOAP packages messages; WSDL describes operations, messages and bindings; UDDI supports service discovery; and HTTP can carry an exchange. REST is an architectural style based on resources, representations and uniform, stateless interactions—not a particular message format.
What is a web service?
A web service is software designed to let separate systems interact over a network. The W3C Web Services Architecture Working Group Note defines one as “A Web service is a software system designed to support interoperable machine-to-machine interaction over a network.” The definition appears in the W3C note published 11 February 2004; it describes a standards context, not a requirement that every modern API use SOAP or WSDL. W3C Web Services Architecture
As an Amazon Associate I earn from qualifying purchases.
It helps to distinguish the service—the abstract functionality—from the agent, the concrete software or hardware that sends and receives messages. An implementation can change while the service’s intended functionality remains the same. A message carries application-specific information; it might be an HTTP GET request, an XML document or a SOAP message.
How the standards fit together
These terms refer to different roles, not one compulsory stack. A client needs to know what exchange to make and how to make it. A description can document the interface; a message framework can package an exchange; a carrier can transmit it; and a discovery mechanism can help the client locate a provider.
#1 Best Overall
- SOAP packages messages. SOAP 1.2 is an extensible framework for exchanging XML messages. It can use different network protocols to carry those messages.
- WSDL describes an interface. It specifies messages and operations, then can bind the abstract description to concrete protocols, formats and endpoints.
- HTTP can carry interactions. It is distinct from both the message structure and the interface description.
- UDDI supports discovery. It specifies ways to describe and discover providers, their services and technical interfaces.
- REST describes an architectural style. It organizes interactions around resources and representations, using a uniform interface and stateless interactions.
The W3C architecture note discusses SOAP and WSDL in the context of web services and also covers REST-style services. The WSDL 1.1 note, published 15 March 2001, describes SOAP 1.1, HTTP GET/POST and MIME bindings. UDDI Version 3.0.2 describes service-provider and interface discovery. None of these sources makes UDDI, SOAP or WSDL mandatory for every web service. W3C WSDL 1.1 · OASIS UDDI Version 3.0.2
SOAP versus REST: what is the difference?
SOAP and REST describe different kinds of choices. SOAP is a message framework: it defines how a message is packaged. REST is an architectural style: it emphasizes resource identifiers, representations, a uniform set of interaction semantics and stateless interactions. It is therefore misleading to treat REST as a wire protocol or as another name for JSON. Representations can take different forms.
Rank #2
They are not necessarily mutually exclusive labels in every implementation. The W3C architecture note says SOAP can be used in a REST-consistent way or in a way that is not REST-consistent. To compare two designs, ask about their interaction model, message format, interface description, carrier, discovery needs and operational requirements rather than relying only on “SOAP or REST.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Is SOAP the same as HTTP?
No. SOAP defines a message framework; HTTP is one possible protocol used to carry an interaction. The W3C architecture note identifies HTTP as common in its discussion, but does not make it synonymous with SOAP or the only possible carrier. WSDL 1.1 also specifies HTTP GET/POST bindings alongside SOAP and MIME bindings. A reference to SOAP alone therefore does not tell you which transport a system uses.
Rank #3
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
What does WSDL describe?
WSDL, or Web Services Description Language, describes the messages and operations a service exposes. It can connect an abstract interface to concrete details such as the message format, protocol binding and endpoint. A client can use that description to understand how to form an exchange, but WSDL does not itself carry the exchange or perform the service operation. The W3C’s WSDL 1.1 note sets out this abstract and concrete description structure. W3C WSDL 1.1
What is UDDI used for?
UDDI is a specification for describing and discovering service providers, the services they offer and the technical interfaces used to access them. Its role is discovery, not message packaging or transport. UDDI belongs to the traditional web-services standards landscape, but its specification does not mean every service must register with or depend on UDDI. OASIS UDDI Version 3.0.2
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
How to evaluate a web service design
For a concrete system, separate the questions that are often collapsed into a single protocol label:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteQuick Recap
Best Value
- Interaction model: Does the design invoke named operations, organize access around resources, or combine approaches?
- Messages and representations: What information is exchanged, and in what format? SOAP supplies a message framework; REST does not prescribe JSON as its sole representation.
- Interface description: Is the interface machine-described, and does that description identify operations, formats, bindings and endpoints?
- Transport: Which network protocol carries the messages? Do not assume HTTP solely because SOAP is involved.
- Discovery: Must clients find providers or interfaces through a discovery mechanism, or are endpoints configured another way?
- Operational needs: Assess security, reliability, compatibility, scale and tooling for the specific deployment. The cited architecture and standards documents explain the concepts; they do not establish a current performance ranking or a universal recommendation.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
