We have a conventional application built using ASP.Net Web forms which uses SQL Server for database. Reports are generated using SSRS. We have a main table called ManifestContainerDetails - this table is for reporting purpose. When shipping is done for a manifest, it’s component details will be stored in this table. This data is not changed by the system once shipment is done.
There are many reports based on this table. And many users access the same report. The table is huge – but most of the time users will be interested in reports for manifests that are shipped within last one week. So, most of the time the users are requesting for same resource with multiple representations.
This looks like good opportunity for caching the resource. And
REST promises caching by utilizing the capabilities of
http intermediaries. Things Caches Do - Ryan Tomayko and What and Where are Intermediary HTTP Caches
I found an article REST Reporting - Eric Gropp which says about creating a report from multiple resources using XSLT.
Now I have following questions, while I am in front of a black board, to design a feasibility study:-
- Is it a feasible idea to make my above scenario as a REST service and create reports based on that?
- Is caching possible in such scenario?
- Is tools available to generate advanced reports based on multiple REST Resources?