Laws of SOA

Date: ~2008 Slides: slideshare.net/totto

SOA projects fail when they optimise for architecture over business value. This talk cuts through that pattern: how to define services that matter, establish governance that works, and understand what SOA can and cannot actually deliver.

What the talk covers

Why SOA projects fail. Most failures trace back to the same root cause — teams build technically correct SOAs that do not deliver real business value. The talk names the failure modes and explains why they happen.

Defining services and service categories. The hardest part of SOA is not the plumbing — it is deciding what a service actually is. Clear service categories and boundaries are the foundation everything else depends on.

Governance that functions. SOA governance is frequently treated as bureaucracy. The talk distinguishes governance that enables good decisions from governance that blocks them.

The difference between a normal SOA and a "real value" SOA. What distinguishes architectures that become assets from those that become liabilities. SOA maturity models and what they reveal about where an organisation actually is.

Concrete examples. Cases where SOA delivered measurable value — and the patterns those projects had in common.

Language: English

---