The industry as a whole has been attempting to define Services Oriented Architecture (SOA). The definition of SOA may wary based on the responsibility of the individual. It is therefore necessary to understand the responsibilities of the stakeholders before defining SOA. The following link to the document is an attempting at identifying the various stakeholders.
http://www.soablueprint.com/whitepapers/SOAStakeHolders.pdf
Practitioners observations and view on the best practices, key learning on the fast changing landscape of technology and architecture. - Strategic User of Information Technology - Cloud Computing - Big Data
Monday, July 24, 2006
Subscribe to:
Post Comments (Atom)
Key Learnings - Using EDA to implement the core SOA principle of "loose-coupling"!!!
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
The purpose of this blog is to get some validation for how I look at Business Processes vs. Business Services. In simple terms, I differen...
-
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
One of the key ingredient for success is clearly defining the roles and responsibilities within IT. There are multiple stake holders in IT w...
2 comments:
Post a Comment