locked
Is AppFabric Caching appropriate? RRS feed

  • Question

  • I'm realtively new to caching, so please excuse if this is a dumb question...

    I have an application that has around 3m (read and write) trx per day and have been in the process of taking these from our on-site sql/san to the azure cloud.  Given that this data is constantly being updated and the relatively cheap costs of table transactions, we were thinking of breaking out these high transactional tables into the azure table storage.  

    Would caching be more appropriate?  Would it still be appropriate if the data updated after each read?  

    It has always been my impression that caching best used when data is not frequently updated.  If this is not the case, what is an example where caching would not be appropriate?  Thanks!

    Tuesday, July 26, 2011 1:01 AM

Answers

  • Hey Jcorbs

    caching might still hold good in your application depending upon what you are caching ....  If the data is updated after every read , you should NOT have it in cache.

    it would become a costly affair, as you would not get performance incentive and number of cache access would become high.

    - cahing should be used when you have some static content like drop down values which are going to remain same say member country or an information that does not change very frequently like popular or most read article ( the way this site displays in the right pane )

    - some static pages which might have images but information on which remains same as we have in Photo Gallery, Take a tour kind of links.. also make ideal candidate for cache.

     

     

     


    Arora S

    • Marked as answer by jcorbs Monday, August 1, 2011 12:40 AM
    Tuesday, July 26, 2011 6:27 AM

All replies

  • Can you elaborate more on what is done with the data after the transaction completes?  

    AppFabric Caching is best suited for temporary storage of data and is great for saving a trip to persistent storage for data that is accessed frequently within a short period of time.


    Auto-scaling & monitoring service for Windows Azure applications at http://www.paraleap.com
    Tuesday, July 26, 2011 3:18 AM
  • Yes, as you said, Caching is not appropriate here and it would be a costly affair. You are not going to use any static content here. All the content are so dynamic for reading. Whenever you have good chunk of static content (or less updated data), then it is adviced to go for caching otherwise it will hit the performance (and cost) instead of improving the perf.

    Thanks,

    Seetha

    ----------------------------------------------------------------

    Please 'Vote As Helpful' if this helps you in resolving your query.

    Tuesday, July 26, 2011 5:14 AM
  • Hey Jcorbs

    caching might still hold good in your application depending upon what you are caching ....  If the data is updated after every read , you should NOT have it in cache.

    it would become a costly affair, as you would not get performance incentive and number of cache access would become high.

    - cahing should be used when you have some static content like drop down values which are going to remain same say member country or an information that does not change very frequently like popular or most read article ( the way this site displays in the right pane )

    - some static pages which might have images but information on which remains same as we have in Photo Gallery, Take a tour kind of links.. also make ideal candidate for cache.

     

     

     


    Arora S

    • Marked as answer by jcorbs Monday, August 1, 2011 12:40 AM
    Tuesday, July 26, 2011 6:27 AM