> 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.
>
I think that depends on how you model this thing. What if I make it
something equivalent to a "compliance log" or "action archive" which I
post stuff into via a well-defined interface.
If I apply what Amazon are doing, I'd have a team responsible for that
service and the associated data mining tools which they'd make available
to their "clients". Alternatively, I might have the service publish an
additional "analysis" interface which allows people to obtain reports
based on the data but no direct access to the data, no SQL etc.
The cost of course is that one can't have too many kinds of report too
quickly but the benefit is looser coupling, easier maintenance etc.
> 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?
>
Strikes me you might have several such services each holding certain
kinds of data and offering "query interfaces".
Or you could arrange for each of the services that generate such
information to hold it themselves and provide suitable reporting.
Or you could have each service publish some kind of RSS feed decoupling
the storage responsibility from the publish/generation responsibility.
And there could be multiple subscribers and therefore multiple stores
with multiple different kinds of report.
> 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.
>
Architecturally, I think it can be made to work in most cases one way or
another but it's gonna be a tradeoff between centralized versus
scattered versus flexibility of reporting etc.
Dunno if that helps,
Dan.
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.
