On May 31, 2006, at 7:39 PM, Stefan Tilkov wrote:
>
> 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.
...sometimes it looks like there is some kind of masoistic enjoyment
involved...:-)
>
> 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.
>
I am not sure if the required modeling effort would even be an
option: lack of experience, lack of resources, lack of coordination
between stackeholders of the model, even if it is not a fully blown
domain model.
Also still very theoretical, but:
- it seems attractive to apply the 'service management'/'SOA
governance' ideas from the
SOA camp to managing the source system 'API' (even if that is the
physical data model).
- in the long run I imagine decentralized approaches to play a
significant role in dealing
with those local SQL/XML interfaces spread all over the
enterprise. Centralized coordination
simply seems like a bad fit for the ever increasing heterogeneity
and demand for integration.
(Have a look at zLab[1] of Commerce.net for more in-depth treatment)
I know this is vague, but hopefully it adds something to this thread..
Jan
[1] http://zlab.commerce.net/
> 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
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor --------------------
> ~-->
> Get to your groups with one click. Know instantly when new email
> arrives
> http://us.click.yahoo.com/.7bhrC/MGxNAA/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.
