I have searched all the posts related to Azure with memcached server, and it seems like the only version that works in Azure is 18.104.22.168 from http://jehiah.cz/projects/memcached-win32/
I was trying to use the latest version of memcached server 1.4.5. It works in development fabric, but not in Azure. Has anyone successfully use 1.4.5 with Azure? If so, how do you do to make it work?
How I tested in development fabric is as follow
1. Downloaded Windows Azure Memcached Solution Accelerator http://code.msdn.microsoft.com/winazurememcached
2. Downloaded v1.4.5 windows binaries from http://labs.northscale.com/memcached-packages/
Windows, (64-bit) zip file memcached-1.4.5-amd64.zip
According to memcached.org, it says NorthScale builds memcached binaries for windows platforms.
3. Include 1.4.5's one binary(pthreadGC2.dll) and memcached.exe in WorkerRole project (Build Action:
Content , Copy to Output Directory : Copy Always )
4. Compile and run
it all worked fine in Dev Fabric, but not in cloud.
Is there any other version of memcached server that I can use or I have to stick with 22.214.171.124.
Or maybe there are others that are better than memcached?
As I recall, newer versions of memcached try to use local ports via the loopback address and thus don't work in Windows Azure (where loopback is disabled). For now, I think you need to stick with the older version of memcached. (We're working
on ways to enable new versions.)
MSFT own "Velocity" is - in my understanding - a considerable ways off yet [>6 months] so Memcache is pretty important for us to reduce cost but most critically improve speed and reliability - so we are really viewing this as a fundamental
hole in our app at the moment that our competitors already have [who are using Amazon, RackSpaceCloud etc].
If we get Memcache working and we are happy with it - we'll probably stick with it and continue using it until MSFT allow the newer versions. It shouldn't then be all that hard to upgrade.
The more people supporting one type of cache - the more reliable it will work on Azure - so I'd stick to cloudcache and help extend it :)