My blog has moved and can now be found at http://blog.aniljohn.com

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Sunday, January 28, 2007
« Unified View of Enterprise Management | Main | SOA Magazine February 2007 Issue »

One of the questions that is often asked by certain folks is the relationship between Enterprise Architecture and Service Oriented Architecture. Some folks believe that SOA is the new version of EA, others that the disciplines are distinct. My personal belief that they are mutually supporting disciplines and the level of maturity that an organization has achieved in one will directly impact its ability to implement the other.

Given this the following quote, from Anne Thomas Manes of the Burton Group, really resonated with me:

"SOA also applies at the enterprise architecture level -- helping the [Enterprise Architects] optimize the application portfolio and data architecture. Nearly every large organization has way too many applications that implement the same capabilities and way too many data structures that represent the same information. The cost of ownership of managing and maintaining a bloated application and database portfolio keeps fixed annual costs very high, reduces the available funds for new projects, and severely limits the flexibility and agility of the organization. From the [Enterprise Architecture] perspective, the goal is to dramatically reduce duplication of application functionality and data structures by implementing shared capabilities as services and designing standard data structures for interfacing with those services. [Enterprise Architects] should be defining priorities for SOA projects.

When it comes time to design a specific application, the goal is to analyze the required capabilities of the application, identify capabilities that have already been implemented, and identify capabilities that other systems might need. These shared capabilities should be implemented as services -- not re-implemented in every application that needs them. Also any volatile capability should be implemented as a service to increase separation of concern and to enable easier management."

Figured I'd put it on the blog as I'm sure that I will be reusing this particular explanation in the future and it will be easier to point to it here with attribution given to Anne.

1/28/2007 11:12 AM Eastern Standard Time  |  Comments [0]  |  Disclaimer  |  Permalink   
Comments are closed.