CODEWITHSUNDEEP
soa
Chris Snow
Chris Snow

Reputation: 24606

reporting functionality in SOA services

I'm looking to design a SOA service which in addition to its main requirements has a requirement for a small number of reports.

When should SOA services (a) include their own reporting functionality, and when should (b) reports be made available as part of a separate reporting service?

I guess (a) makes the service more self-contained, but (b) should probably be preferred when the organisation already has reporting services deployed?

Upvotes: 0

Views: 562

Answers (1)

Arnon Rotem-Gal-Oz
Arnon Rotem-Gal-Oz

Reputation: 25919

You can/should report on individual services if the report is self contained and relates to data that changes frequently.

It is ok to use a centralised reporting when the data is immutable i.e. historic copy of the data. This way the services are still the owners of the data (and responsible for updating the data) and the data is still available for cross-service reports. This is a pattern I call aggregated reporting (you can see a draft of it here)

You can see an article I published on infoQ called bridging the gap between BI & SOA

Upvotes: 1

Related Questions