For many enterprises, trust, or lack thereof, remains the most significant barrier to service-oriented architecture (SOA) adoption.
An SOA initiative is meant to knock down internal barriers and help an enterprise evolve from separate silos of technology and information into a leaner, shared-service organization. However, many application development leaders struggle to create a consistent service architecture that is widely shared, reused, and adopted across internal development teams. Instead, these teams often go rogue, ignoring SOA procedures and swapping out IT toolsets, message formats, and protocols to build their own solutions, which ultimately fail to support enterprise growth.
Read Chris's article on IT Briefecase
|
Date: Tue, 9th Oct, 2012
Level:
Intermediate
Reads: 1422
Discuss this article on Stack Overflow
|
|
|
|
Chris Haddad
VP, Technology Evangelism
WSO2 |
|
|
|
While SOA governance is meant to prevent this destabilization from happening, the tooling, which is typically promoted as a mechanism to enforce best practices, often fails to encourage consumer adoption or even illustrate business value. As a result, the use of SOA governance software is not yet widespread, despite being arguably the greatest indicator of whether an organization is committed to SOA.
Read Chris's article on IT Briefecase
the blog
oh well, i do also agree with