Allow an external endpoint for a dedicated cache role
This would allow multiple deployments to share one dedicated cache role. It also needs to use the Azure shared cache assemblies to do this as currently to change which flavour of caching to use (PaaS versus dedicated roles requires different nu-get packages)
Azure Managed Cache service and Azure Redis Cache Preview, both support sharing of Cache across deployments.
Todd Whitehead commented
The performance and transaction limits of the shared cache services aren't suitable for high volume usage. Supporting access to your dedicated cache roles should be a no-brainer decision MS.
On Sep 3rd, 2013 Microsoft announced Preview of new distributed cache service; Windows Azure Cache Service.
The new Windows Azure Cache Service enables you to easily deploy dedicated, high performance, distributed caches that you can use from your Windows Azure applications to store data in-memory and dramatically improve their scalability and performance.
The new Windows Azure Cache Service can be used by any type of Windows Azure application – including those hosted within Windows or Linux Virtual Machines, as well as those deployed as a Windows Azure Web Site and Windows Azure Cloud Services. Support for Windows Azure Mobile Services will also be enabled in the future.
You can instantiate a dedicated instance of a Windows Azure Cache Service for each of your apps, or alternatively share a single Cache Service across multiple apps. This later scenario is particularly useful when you wish to partition your cloud backend solutions into multiple deployment units – now they can all easily share and work with the same cached data.
You can find more details here:
You can also read ScottGu's blog for more details
Abhinav Gupta (MSFT) commented
The new Windows Azure Cache Service (Preview) that went live yesterday does exactly this and much more (single cache client, robust Monitoring, MSFT managed-cache). Check it out at http://www.windowsazure.com/en-us/services/cache/ and http://www.windowsazure.com/en-us/documentation/services/cache/
I'm completely shocked that this isn't supported in someway. It is not acceptable that applications must be published in a single deployment in order to share the dedicated cache roles. This is obviously a big problem if you're trying to use Azure Web Sites as well.
It would be helpful to allow us to create external endpoints on the roles to allow other systems to share the cache. You can already do this using other caching products on a VM. Why not Azure Cache?
We'll most likely end up going with a CentOS/Redis deployment instead now.
Matt watson commented
Microsoft says dedicated caching performs better and is recommended over the shared cache. But yet dedicated caching only works within a single deployment. Please allow all servers on the same virtual network to access the ports on dedicated cache. No public IP access is needed. Thank you!