1

Why is the New SOA Data Integration Architecture Group on a Roll?

Because there is real need! Period! Even after investing heavily in agile architecture approaches such as SOA, IT organizations are finding it extremely challenging to solve complex data integration issues.

If you are involved in defining or re-defining a data architecture to enable composite applications and portals to effectively leverage data in an SOA, here is where the discussions are happening.

If you are looking to enhance your existing data architecture to ensure that business intelligence reports can quickly leverage data that is not in your data warehouse, you will find your answers here.

These are some exciting discussion threads that are underway on the world’s first SOA Data Integration Architecture Group:
• What do we exactly mean by ‘data integration’ in SOA context?
• Is there any specific difference between the terms ‘service’ and ‘data service’? Or are both synonymous?
• ROI of SOA Data Integration
• ROI of SOA Data Integration Part II: Selling SOA and Data Integration to the Business
• Finding the Intersections of BI and SOA
• What about data abstraction and the cloud?
• Data integration across organizational boundaries…
• Doing Data Virtualization Without Design…Possible?
• EAI, ESB, EAI, ETL, EII – when to use what?

So, come join the group led by David Linthicum and leading industry architects and become a part of re-defining the last mile of SOA – the DATA!

Get started now by signing-up here.

FacebookTwitterLinkedInEmailPrintShare
This entry was posted in Data Integration, Data Services, Data Warehousing, Enterprise Data Management, Integration Competency Centers, Real-Time, SOA and tagged , , , . Bookmark the permalink.

One Response to Why is the New SOA Data Integration Architecture Group on a Roll?

  1. Arvind Kumar says:

    I am not against SOA or DataService approach. But is DataService is answer to all Data integration challenges? Most of the articles I come across on dataservices, made it sound like, Dataservice will solve most of the Data integration and data delivery challenge. My concern is
    1. Assumption made that data is good at different datastore. The only missing part in puzzle is exposing the data. This is not true.
    2. With DataService, your challenge still remains to integrate your data.
    3. Garbage in Garbage out. In theory you can apply in-stream business rule to clean the data. But then you have to apply the business rule for every query or you have to presist the clean data ( traditional ETL).
    4. If for quick delivery, one can expose the data using DataService ( without much data cleaning or standardization), what happens to the data TRUST.
    5. Performance ( in case of Heterogeneous sources)

    By adding DataService to the architecture, we are adding colorful sauce on existing old spaghetti? In long run, is it going to be more difficult to maintain architecture?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>