SOA Pattern of the Week (#3): Domain Inventory

Enterprise-wide harmonization is a desirable and ideal target state that fully supports pretty much everything SOA and service-orientation stand for. For those that have achieved such a state, bless your standardized hearts. You have accomplished something that has eluded many others. However, not attaining this state does not mean you cannot successfully adopt SOA.

In this series

• SOA Pattern of the Week (#1): Service Façade
• SOA Pattern of the Week (#2): Non-Agnostic Context

In some circles it has become common to view an SOA initiative as an all-or-nothing proposition that demands an uncompromising commitment to an enterprise-wide transformation effort. For those that subscribe to this view, it can inspire visions of architects choking at the thought of having to comply to global data models, IT managers losing sleep over having to give up authority over their departments, and rebellious developers being rounded up by the standards police (equipped with industry-standard riot gear, no less).

The misguided association of SOA projects with the infamous "Big Bang" approach is unfortunate. It gives SOA an unwarranted stigma that runs contrary to the very philosophy of service-oriented computing. You are not required to carry out an enterprise-wide adoption of SOA in order to realize its benefits. This is the very reason the Domain Inventory pattern emerged. From a strategic planning perspective, there is (for most organizations) no other pattern as important to fully realizing everything SOA has to offer.

When transitioning toward the adoption of service-orientation, you are responsible for determining the scope of this adoption. As long as it is meaningfully cross-silo, it can realize an extent of the strategic benefits associated with service-oriented computing. In other words, as we just stated: You are not required to carry out an enterprise-wide adoption of SOA in order to realize its benefits. You can establish a domain that represents a manageable segment of your IT enterprise and carry out the adoption within its boundary. Another team within your organization can establish its own domain and carry out its own SOA project independently from yours.

This fundamental concept forms the basis of this pattern, which provides a very real and proven alternative to enterprise-wide adoption.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine