Through ASP.NET 1 to 3.5, output caching was stuck in memory. ASP.NET 4 makes it possible to use custom output-cache providers to use any kind of storage mechanism including databases, local and remove disks and distributed cache engines. In this session, we will build a custom output-cache provider that persists data in local hard-drive and we will learn how to configure an ASP.NET application to use some famous distributed cache engines. This is a coding and configuring oriented session.