Output Caching: This is the simplest type of caching. It stores a copy of the latest HTML rendered page is sent to the client. The next client that submits an application on this page does not run the page. Instead, the final output HTML is sent automatically. The time would have been required to execute the code page and complete recovery.

Data Caching: This type of caching is done manually in your code. To use the data cache, you store important information, which takes time to rebuild (as a set of data from a database) in the cache. Other sites can check for this information and use it, bypassing the steps normally required for download. Caching data is conceptually the same as using the state of implementation, but it is much more user-friendly server because the articles will be removed from the cache automatically when it becomes too large and performance could be affected . Articles can also be set to expire automatically.

Also, two specialized types of caching build on these models:

Fragment caching: This is a specialized type of hide production, rather than the entire page’s HTML, which allows to cache the HTML code for part of it. Fragment caching works by storing the rendered HTML output of a user control on a page. The next time you run the page, the same page events fire (and therefore the page code will still work), but the appropriate code for the user control is not executed.