Regardless of the selected cache mechanism (file or database), the Reporting REST service must be deployed on a single instance in order to have a synchronized read/write access to the cache. Thus my suggestion is to host the service separately and enable CORS
to allow the communication between the viewers and the service.
In addition, note that the HTML5 Report Viewer is not using exactly the MVC architecture. There is a client widget (the viewer) and a service which work combined. To preserve the report between requests we keep its state in cache
. This is what makes the HTML5 Report Viewer suitable for any Web application.
Let us know if you have any further questions.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.