How to use asp.net windows azure cache with multiple instances
Hey guys if I have an azure web application running under multiple instances how can I use the asp.net cache. does azure team have any azure cache providers?
I read somewhere that they will maintain speed in the future, but if I have to live with some application in the next couple of months, what is the best way I can cache my data (I don't want to use a SQL server cache as it is simple defeats my caching goal in the first place)
source to share
There are several options now -
1) Go to azuresqlsession.codeplex.com - a custom session provider that works with SQL Azure. This is much faster than Microsoft's custom provider that works with azure table storage.
2) Also there is "AppFabric Caching" - a distributed cache that runs in azure data centers. Microsoft has also written its own session provider that works with AppFabric Caching. It is currently in the CTP and you can get it here - portal.appfabriclabs.com - there is a good overview of how to use it here - http://blogs.msdn.com/b/windowsazureappfabric/archive/2010/10/ 28 / introduction-to-windows-azure-appfabric-caching-ctp.aspx? Wa = wsignin1.0 - and also in azure sdk 1.3 labs.
I realize the question was asked a while ago - I just thought I'd update it in case someone stumbled upon the question after searching google / bing.
Good times! about.me/ehuna
source to share
I just wanted to update the latest information as I just came across this post:
Windows Azure Cache is up and running in full swing, find out more here:
http://msdn.microsoft.com/en-us/library/windowsazure/gg278356.aspx
Here's an example showing how to use Windows Azure Cache with an ASP.NET application:
- How to add and retrieve an object from the cache
- How To: Expire Object In Cache
- How to Cache ASP.NET Session State
- A practical guide. Keeping the ASP.NET Page Output Cache in Cache
https://www.windowsazure.com/en-us/develop/net/how-to-guides/cache/
source to share
Microsoft plans to implement the Windows Azure Cache provider when ASP.NET Cache Extensibility ships with .NET 4.0.
In the meantime, can you cache separately on a per-instance basis and then perhaps use a queue store to communicate between instances to invalidate the cache?
source to share