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/
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.
