> Hi Stefan,
>
> I'd like to add to this (as I have been working in a DWH context
> the last half year): I am very interested (just have not had the
> time yet) in the question of how SOA based integration can be
> usefully applied to an environment where data storage is so
> dominant that interfacing with other applications is primarily done
> through the ETL (extract-transform-load) processes and the DWH.
>
> In a sense this is 'unidirectional' integration, as information
> just flows from the integrated systems to some consuming system.
> The DWH (and the DWH's physical model) become the central
> integration spot (with all the coupling consequences).
>
> The question is not if that approach is good or not (since that is
> just the way things are and will be done) - the question is how SOA
> concepts can be usefully applied or how SOA ideas can be explained
> to people bound to such an environment?
>
For the DWH folks, getting at the unmodified, unfiltered,
unaggregated back-end data seems to be seen as absolutely mandatory
-- which is somehow understandable. Still, every change to an
application leads to changes in the ETL processes, which creates a
lot of work for them.
One approach might be to offer them a stable interface across
implementation versions, which puts some burden on the application
developers, but decouples the DW from the system's internals. Whether
that interface is SQL or XML is (logically) irrelevant.
Note that this is still rather theoretical at the moment ...
Stefan
> Jan
>
>> I'm looking for thoughts on possible integration/co-existence/
>> conflict issues of SOA and ODS (Operational Data Store) concepts.
>>
>> An ODS as a centralized, up-to-date, hybrid OLAP/OLTP store for
>> status data (without history) is appealing because it can be the
>> point of consolidation for information spread throughout the company
>> (e.g. for issues such as fraud detection, compliance issues etc.). On
>> the other hand, it seems to violate the idea of loosely-coupled,
>> independent services with managed dependencies -- after all, the
>> central storage might be abused (on purpose or accidentally) for
>> integration tasks.
>>
>> What do you think? Is an ODS something that you would avoid in an
>> ideal SOA scenario? Or do you consider it a vital piece an any decent
>> company's IT environment?
>>
>> Personally, I'm still undecided. I have a strong fear of creating a
>> huge, monolithic, centralized bottleneck and maintenance issue, while
>> on the other hand I can't seem to be able to find a good "pure SOA"
>> alternative.
>>
>> Thanks,
>> Stefan
>>
>> --
>> Stefan Tilkov, http://www.innoq.com/blog/st/
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor --------------------
> ~-->
> You can search right from your browser? It's easy and it's free.
> See how.
> http://us.click.yahoo.com/_7bhrC/NGxNAA/yQLSAA/NhFolB/TM
> --------------------------------------------------------------------
> ~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
