Web Services Introduction — Machine-to-Machine Communication Standards

In this tutorial, you will learn about Web Services Introduction. We cover key concepts, practical examples, and best practices to help you master this topic.

Web services provide standardized communication between machines over networks using XML-based protocols like SOAP and WSDL, with formal contracts ensuring reliable integration.

What You'll Learn

• What web services are and how they differ from web APIs
• The SOAP, WSDL, and UDDI stack
• When to use web services vs REST or Graphql

Why It Matters

Many enterprise systems in banking, insurance, healthcare, and government use web services. Understanding them is essential for enterprise integration work.

flowchart LR
    A["Service Provider"] --> B["WSDL\n(Contract)"]
    B --> C["UDDI\n(Registry)"]
    C --> D["Service Consumer"]
    D --> E["SOAP Messages\n(XML over HTTP)"]
    E --> A
    style A fill:#dbeafe,stroke:#2563eb

Real-World Use

DodaTech's Durga Antivirus Pro integrates with enterprise security partners using SOAP web services for threat intelligence sharing, where formal contracts guarantee reliable data exchange.

Code Examples

# Simple web service call (SOAP)
import requests

url = "https://example.com/webservice"
headers = {"Content-Type": "text/xml; charset=utf-8"}
body = """<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetQuote xmlns="http://example.com/stockquote">
      <Symbol>ACME</Symbol>
    </GetQuote>
  </soap:Body>
</soap:Envelope>"""

response = requests.post(url, data=body, headers=headers)
print(response.text)

# Calling a web service with curl
curl -X POST https://example.com/webservice \
  -H "Content-Type: text/xml; charset=utf-8" \
  -H "SOAPAction: GetQuote" \
  -d '<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetQuote xmlns="http://example.com/stockquote">
      <Symbol>ACME</Symbol>
    </GetQuote>
  </soap:Body>
</soap:Envelope>'

Common Mistakes

1. Using SOAP When REST Would Suffice

SOAP adds complexity that simple CRUD APIs don't need.

2. Ignoring WSDL Changes

WSDL defines the contract. Changing it without versioning breaks all clients.

3. Not Understanding SOAP Namespaces

Missing or incorrect XML namespaces cause Parsing failures.

4. Assuming Web Services Are Obsolete

Many enterprise systems still require SOAP-based web services.

5. Underestimating XML Overhead

SOAP messages can be 10x larger than equivalent JSON, impacting performance.

Practice Questions

1. What are the three main components of the web services stack?
2. How does SOAP differ from REST?
3. What is the purpose of WSDL?
4. Why do enterprises still use SOAP?
5. What protocols can SOAP use besides HTTP?

Answers:

1. SOAP (messaging), WSDL (contract), UDDI (registry).
2. SOAP is a protocol with formal contracts; REST is an architectural style.
3. WSDL defines the service contract including operations, messages, and endpoints.
4. For formal contracts, built-in security, ACID transactions, and regulatory Compliance.
5. SMTP, JMS, TCP, and any transport protocol.

Challenge: Create a simple SOAP web service that accepts a stock ticker symbol and returns a price. Write both the server and a client that calls it.

FAQ

What's Next

Learn about SOAP and XML message structure, then explore WSDL Contracts.