Home/ Questions/Q 5938757
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T15:43:51+00:00

Our web application is deployed in a web farm (more than 20 servers). The

  • 0

Our web application is deployed in a web farm (more than 20 servers). The site has a huge traffic (millions of page views per day).
In the first release, this application is using EntLib’s CacheManager (Entreprise application block caching). We call this “Local Server Cache”. There are many benefits but we still have a major drawback : each server manage its own cache and acces to database (not distributed).

That’s why we are trying to implement AppFabric caching feature in order to reduce database round trips. One of the major problem we have is data synchronisation :

  • with GetAndLock/PutAndUnLock (aka distributed lock) page response time is higly affected
  • with Get/Put + simple server side lock, we have so many requests with the local cache ; no benefits.

So what are caching stragegies for large scale web sites ?

Thanks,

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As I’d mentioned on MSDN, immediate consistency is expensive. You have to accept some tradeoffs in consistency, or lay out a lot of cash to be immediately consistent. Using the isolated read/write model we discussed on MSDN, along with queues, probably provides you the best performance/consistency bang for the buck. Multiple tiers of cache as suggested by David are also excellent, depending on your overall architecture/design. Using your own local in-proc or localhosted cache implementation also offers a lot of value — not a fan of AppFabric’s OOTB local cache myself.

    –ab

    • 0