Architecture · 2000–2016 · Web Boom
SOAP / WS-*
Enterprise web services with ceremony. Interoperability theater with XML envelopes.
SOAP failed because debugging required XML archaeology and vendor certification, not curl and logs. WS-* stacked specs faster than teams could implement them. REST won by being observable; SOAP won RFPs and lost engineers.
Cost of the fad
Banks and governments sunk fortunes into WS-Security, WSDL toolchains, and vendor stacks — then quietly rebuilt on REST/JSON while still paying maintenance on the old bus.
Case studies
Patterns
Context
The browser ate the desktop
The web became the default delivery surface. LAMP and Rails made shipping cheap; Ajax made pages feel like apps; SOAP/SOA tried to enterprise-ify the wire. REST won by being debuggable with curl. This decade invented the modern product cadence — and the habit of treating every new framework as destiny.
Compare with
Related
Architecture · 2003–2015
Enterprise SOA
Reuse via shared services — in theory. In practice: central buses and political ownership fights.
$ ESBs, governance boards, and "service portfolios" burned seven-figure programs. Many orgs got distributed monoliths with worse latency and a permanent integration team.
Architecture · 1991–2008
CORBA
Language-agnostic distributed objects. Complexity scaled faster than value for most shops.
$ Enterprises spent years on IDL, ORBs, and vendor lock-in for distributed objects that SOAP and REST later made look quaint — after the invoices cleared.
Architecture · 2000–now
REST / HTTP APIs
Resources over RPC theater. Won the API wars by being boring enough to debug with curl.