Architecture · 2002–2016 · Web Boom
Enterprise Service Bus (ESB)
Message bus in the middle of everything. SOA's plumbing invoice with vendor licensing.
Why Enterprise Service Bus (ESB) became a costly fad
ESB failed because centralizing every integration turn creates a queue-owning empire that slows change. REST and async messaging at the edges beat XML orchestration in the middle. The pattern repeated as service mesh before teams learned the same lesson cheaper.
Cost of the fad
What Enterprise Service Bus (ESB) cost
Middleware vendors sold central buses that became single points of failure and political bottlenecks. Integration teams grew; end-to-end latency did too.
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 · 2000–2016
SOAP / WS-*
Enterprise web services with ceremony. Interoperability theater with XML envelopes.
$ 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.
Architecture · 2012–2023
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most. Consolidation and monolith return are the 2020s epilogue.
$ Teams split 4-person products into 40 services, then hired SREs to babysit the mesh. Many later consolidated — after years of distributed tracing invoices and on-call trauma. See case studies on premature microservices and big-bang cutovers for named failure modes.