Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

A Short History of SOAP and Why It Exists

Follow SOAP from 1998 to today, learn the problem it solved, what the letters mean, and why it is still used, with runnable examples that turn function calls into XML.

In the late 1990s, companies wanted their programs to talk to each other across the internet, but every platform had its own remote-call system: DCOM on Windows, CORBA in the enterprise, RMI in Java. They were binary, they were tied to one vendor or language, and firewalls blocked their ports. The one thing every firewall allowed was HTTP on port 80, and the one text format everyone was learning was XML. Put them together and you get SOAP.

SOAP originally stood for Simple Object Access Protocol. Since version 1.2 the letters mean nothing: it is just "SOAP", because it was neither simple nor about objects. What matters is the idea: a standard XML envelope that carries a request or a response between programs, over any transport.

A timeline

timeline
    title Milestones of SOAP
    1998 : XML-RPC drafted
    1999 : SOAP 0.9 from Microsoft, DevelopMentor and UserLand
    2000 : SOAP 1.1 submitted to the W3C
    2001 : WSDL 1.1 published
    2003 : SOAP 1.2 becomes a W3C Recommendation
    2004 : WS-Security 1.0 approved by OASIS
    2007 : WSDL 2.0 Recommendation
    2010s : REST and JSON take over public APIs
    Today : SOAP stays in banking, telecom, government, healthcare

SOAP 1.1 and WSDL 1.1 are still the versions found in most real services.

The problem SOAP solved

Imagine a bank and an insurance company. Their systems were written fifteen years apart, in different languages, on different operating systems. They need to exchange claims and payments reliably. They need:

  • A common message format that any language can produce and read: XML.
  • A common way to describe operations, so developers do not read PDF manuals: WSDL.
  • A common way to report errors, so a failure on the far side is understood: the SOAP Fault.
  • A way to attach security, routing and transaction information without changing the business data: the SOAP header, and the WS-* standards that use it.

SOAP delivered all four. The cost was verbosity: a one-number answer is wrapped in an envelope, a body and several namespace declarations.

What a function call looks like as XML

The easiest way to understand SOAP is to see an ordinary function call turned into XML. This program takes a function name and its arguments and writes them as a SOAP 1.1 body. It is a toy encoder, but it shows the principle of every SOAP library: method name becomes an element, arguments become child elements.

Node.js Function call to SOAP request

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Notice Tea & Biscuits became Tea &amp; Biscuits: XML reserves & and <, so values must be escaped. Forgetting this is the most common bug when people build SOAP messages by gluing strings together.

The same call in older and newer styles

To see why SOAP seemed heavy and why it also seemed safe, compare the same call written three ways.

Node.js One call, three wire formats

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

SOAP is the largest of the three. In return, the envelope has a place for headers (security tokens, routing, transaction ids), a standard fault format, and a link to a typed contract. XML-RPC has none of that. JSON is the smallest and the easiest, and it leaves contracts and extra features to other tools.

Where SOAP is used today

New public APIs mostly choose REST and JSON. SOAP survives, and often thrives, where its strengths matter:

  • Banking and payments: many bank, card-scheme and SWIFT-adjacent integrations are SOAP, using WS-Security signatures.
  • Government and healthcare: tax filing, customs, and health-record exchange often mandate SOAP and WSDL.
  • Telecom and travel: billing systems, airline reservation systems and hotel channel managers.
  • Enterprise platforms: SAP, Oracle, Salesforce (a SOAP API next to its REST API) and Microsoft Dynamics expose SOAP endpoints.

Because these systems run for decades, learning SOAP is not about nostalgia: you will probably be asked to call or maintain one.

SOAP is a protocol (a message standard), not a product. Axis2, Apache CXF, WCF, JAX-WS, Zeep, PHP's SoapClient and .NET's service references are tools that read and write SOAP. You can speak SOAP with nothing but an HTTP client, as this track will show.

What you will learn next

The rest of this chapter builds a working SOAP exchange on loopback so you see every byte. Later chapters study the XML, the WSDL contract and WS-Security in detail. When you reach Projects and Practice you will have the vocabulary to build a complete service.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why did SOAP choose HTTP and XML in the 1990s?

    Binary remote-call systems were blocked by firewalls and tied to one platform. HTTP passed firewalls and XML worked everywhere.
  2. 2. What do the letters in SOAP mean in version 1.2?

    From SOAP 1.2 the acronym was dropped, because the protocol was neither simple nor limited to objects.
  3. 3. Which of these is a feature SOAP offers that plain XML-RPC does not?

    SOAP has an optional header block for extensions such as security, and a defined Fault element. XML-RPC has neither.
  4. 4. What must you do to the value Tea & Biscuits before placing it in an XML element?

    The characters & and < have special meaning in XML and must be written as & and < inside text.

Summary

  • SOAP appeared around 1999 to give programs a standard, firewall-friendly, platform-neutral way to call each other.
  • A SOAP message is an XML envelope; its body holds the method call or the result.
  • WSDL describes services; WS-* standards add security, reliability and more.
  • SOAP is verbose compared with JSON, and richer in standards.
  • It remains common in banking, government, healthcare, telecom and enterprise software.

Next: How a SOAP Call Works