Anecdotally, at least, most customers don’t seem to be buying the single-vendor proposition. Many understand that to identify, say, one company’s ESB as the “backbone” of an SOA flies in the face of the radically simple SOA concept: an array of interoperable, XML-based services strewn across an ordinary IP network, ready to be consumed by applications. The orchestration and Java-based messaging capabilities of an ESB may be beneficial for some subset of related services, but SOAs are ever-expanding, and extending the same ESB everywhere would incur an absurd amount of overhead.
The new focus on governance is a healthy trend. Keeping service end points robust, after all, is what governance is all about. And the fact that many organizations are already thinking hard about service metadata -- how to use it to monitor, manage, and refine an SOA -- is a good indication that things have moved beyond the beginning phases.