MID302: AppFabric Caching: How It Works and When You Should

MID302
Users
• Need to route users to same
machine (i.e. sticky sessions)
Web Tier
• Each machine round trips for data
• Some data might be expensive to
retrieve
• Cached data is typically stored in
the memory of one (each) server
Database
• CPU and disk can get saturated
with an increase in traffic
Users
Web Tier
Caching
Tier
Database
• No stick load balancing needed
– all servers have copy of
cached data
• Easy access to cache cluster
• Multiple machines means scale
and potential for high-availability
• More machines == more
memory for cache objects
• Reduces load on database
<sessionState mode="Custom" customProvider="SessionStoreProvider">
<providers>
<add name="SessionStoreProvider"
type="Microsoft.ApplicationServer.Caching.DataCacheSessionStoreProvider,
Microsoft.ApplicationServer.Caching.Client, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" cacheName="BlueYonderSession"/>
</providers>
</sessionState>
Windows Azure Platform Training Kit
Windows Server AppFabric Training Kit
BizTalk 2010 Developer Training Kit
AppFabric Team Blog
Windows Azure AppFabric on MSDN
Windows Server AppFabric on MSDN
http://northamerica.msteched.com
www.microsoft.com/teched
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn