Skip to main content

Enterprise Information and SOA

Almost every Information Technology implementation and IT Architecture includes Information and Data. SOA is not an exception.

The following sections will highlight some important aspects relating SOA to Enterprise Information.

SOA and Enterprise Information Integration (EII)

I recently read an Aberdeen Group Survey published in February 2008. The survey title is Enterprise Information Integration: The Foundation for Business Success and Transformation.

While reading it I almost thought I am reading about SOA:

  • Abstraction

EII is an integration architecture abstracting the data source.

  • Agility and Business Responsiveness

This Abstraction Layer is Business Responsiveness and IT Agility enabler.

  • Black Box - Data Consumers are not aware of the information sources, Information infrastructure (e.g. databases) and location (e.g. specific instance of a database or a specific file) could be changed without changing the consumer interface.
  • EII federated data approach is replacing a Monolithic data model based on consolidating data relating to an application in a dedicated database or set of tables (the Monolithic approach analogy is not perfect usually data is less monolithic than application functionality).
  • Reuse

One of EII's implementation goals is increasing Data Reuse ratio, very similar to the concept of Service Reuse in SOA.

  • Messaging

Messaging or data transfer is a core mechanism.

It should be noted that there is no free lunch: The price of Abstraction both for SOA and EII is overhead. The EII approach is gradually replacing the monolithic approach of a Consolidated Database. Due to high Data growth rate and growing data Complexity the choice is mainly between these two approaches: Consolidate data in one or few databases in order to simplify the architecture or Abstract Data Integration model. In addition to lack of Agility, disadvantages of the consolidation model could be time and cost of the consolidation process and possibly Performance issues due to database contention. Notice that these approaches are not mutual exclusive: applying EII does not necessarily imply no data consolidation. It should also be noted, that the consolidation model is restricted to structured information supported by current databases mechanisms unlike EII model which may support less structured data sources.


Services can be classified to four categories: New, Wrapped, Composite and Data. The forth service type is an overlap between EII and SOA: Data Services which are part of the SOA architecture and implemented by using EII.


SOA and Information Architecture

One of the Best Practices for SOA implementation is to begin with defining the Data Architecture. Information Services are part of the overall SOA architecture. Data sources outside the enterprise boundaries are the origin of some of the information retrieved or updated by these services.

According to a recent Gartner Research Note (Predicts 2008: Emerging Trends Force a Clearer and Deeper Focus on Enterprise Architecture) 80% of SOA design issues are Enterprise Information Architecture (EIA) issues. This finding is based on feedback from successful SOA implementations. Another prediction is that by 2010 most Enterprise Architecture teams will spend on EIA as much time as they currently spend on Technical Architecture. Architecture teams will have to address new information challenges derived from the new Data Architecture (e.g. Governance, Security etc.). Inability to address them due to lack of formal processes for Information Architecture will be the root of SOA initiatives failures.


SOA and Metadata

Metadata or Data on Data is an important element of SOA architecture and implementation. Metadata describes the components of SOA architecture and the underlying IT assets. SOA messages include both data and the meaning of the data i.e. metadata. The information in metadata is the key for Visibility of SOA abstractions.

SOA and Master Data Management (MDM)

MDM could be a prerequisite for SOA in order to preserve a reasonable level of data consistency and data quality. The Federated model behind EII requires one source for representing single information "truth". Mastering the MDM which maps and describes major data sources serves as this single source. Lack of adequate MDM implementation may result in ineffective Data Services and other SOA services (Functionality related Services also rely on information processed by them).

In summary, information and information on information plays an important part in SOA architecture design and in SOA implementation.

Labels:

Comments

Post a Comment

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...
16 comments
Read more

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...
11 comments
Read more

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...
8 comments
Read more