I have a web application that retrieves data and displays the results. Due to the nature of the business, all business rules are included in the dll from which the web application must extract. Since there are several sites, and we do not want to include the main DLL in all the many applications that have been deployed, we combine any calls into the dll core into a web service. This helps when updating the base dll, which you need to click only one new application (i.e. Web service).
With this architect, I discovered that anyone who logs into any web application makes several calls to the database to get the data, which is then parsed. Information about the data in question is changing slowly, and I only need to update it, perhaps every 4-6 hours.
I am familiar with storing such things in a session when a user wants to see different representations of the same data type. However, the webservice is not actually applied with the session. What is a good method of caching data in a web service so that we do not make multiple expensive trips to the database.
The web service and applications are in C # and ASP.NET 2.0, and we use VS2005.
source
share