Silver-bullet architecture
The belief that one diagram — SOA, microservices, serverless — solves organizational dysfunction without changing how teams ship.
Silver-bullet architecture is what happens when a complex business problem gets renamed as a topology problem. The board sees spaghetti integrations and hears "microservices." The CIO sees batch jobs and hears "event-driven." Nobody asks who owns the reconciliation when two systems disagree at month-end.
The pattern repeats because architecture slides travel better than org charts. A vendor can sell a reference architecture in an afternoon; restructuring teams takes quarters and bruises egos. So the box diagram changes while the same committee approves every deploy, and the new platform inherits the old bottlenecks with fresher logos.
Historically this is CORBA becoming SOA becoming "domain-driven microservices" without ever writing down the domain. Each wave brought genuine ideas — interfaces, bounded contexts, independent deploys — and each wave got purchased by companies that skipped the hard parts and kept the slide.
The tell is universal: success metrics are "number of services" or "percent on cloud," not customer outcomes or incident rates. The cure is boring — clear ownership, incremental migration, and architecture that fits headcount — but boring does not keynot.
Exhibits
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 · 2012–now
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most.
$ 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.
Architecture · 2015–now
Serverless-first
Functions as the unit of deploy. Brilliant for spikes and glue; awkward as a whole product architecture.
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–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.
Platform · 2014–now
Kubernetes
Container orchestration that became the cloud's OS. Overkill for many; unavoidable for many others.
Architecture · 1970–now
Modular monolith
One deployable with clear boundaries. The unfashionable default that keeps shipping while microservices argue about ownership.
Framework · 1999–now
J2EE / EE frameworks
EJB-heavy stacks taught a generation that XML config was architecture. Spring and lighter runtimes absorbed the survivors.