> I was not clear enough. ServiceA, ServiceB, and ServiceC etc.
> provide, as part of their service interface, 'give me all data I
> want' and 'keep me updated on all changes' capabilities via pox/
> http. Reporting ServiceR gets the data and stores them (no problem
> with rdbms here because it is internal ServiceR logic). Within
> ServiceR you use whatever tools/technologies you want for data
> analysis. Results are provided via ServiceR's interface to users.
> If you have only one ServiceA then this approach is an overkill and
> you do data analysis right over the ServiceA's database. Does this
> make sense? -Radovan
>
Ah, I see. Sure, it does make sense - but requires ServiceR to get
data as XML and write query logic in XPath or XQuery. Where this is
acceptable, your solution is fine.
--
Stefan Tilkov, http://www.innoq.com/blog/st/
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.
