05 Juli 2012 8:00I'm researching the option to use the caching feature to cache data while it is being worked on in an Azure cache and upon completion adding the result to storage and/or sql azure. To limit data loss I would opt to use the backup roles featues. What is unclear from the docs is related to eviction and callbacks. I can use AddItemLevelCallback to be notified of items being evicted, but will I will (automatic) evictions by the cache trigger the same callback(s)?
06 Juli 2012 2:17
When you add ItemLevelCallBack for operation removeitem, you will be notified for both when object is removed by you/when object is expired/evicted and hence, cleaned up by cache cluster.
Can you please clarify your scenario and question a bit more?
- Ditandai sebagai Jawaban oleh Bjorn C. Coltof 07 Juli 2012 11:14
07 Juli 2012 11:14In our scenario we are dealing with a piece of state (that we can't eliiminate) that takes so much time to deserialize that we are looking at storage alternatives that will minimize the time spent retrieving the raw data to eliminate that part of the process as much as possible. My initial thought was to use caching for that and have item level callback to push the item to blob/sql in case of eviction, but sadly the removal callback does not supply the item being removed only the key. We can still use the caching feature, but at the same time we still need to serialize state to another storage service so we can handle automatic evictions and restore from the secondary medium in that case.