Cache
Azure Cache is a family of cache offerings that support high throughput, low-latency data access, to enable building fast, scalable applications.
- Azure Redis Cache (Preview) is based on the popular open source Redis Cache engine. The service gives users access to a secure, dedicated Redis Cache, managed by Microsoft.
- Azure Managed Cache Service: Built on App Fabric Cache. This is a dedicated managed service.
- In-Role Cache: Built on App Fabric Cache. This is a self-hosted cache, available via the Azure SDK.
-
Redis Cache should also support persistence
Redis supports persistence and not acting as a cache (with a LRU key eviction policy).
I would like to be able to provision a Redis cluster that never drops data added to it.
577 votesRedis persistence is now supported in Azure Redis Cache. Please see this for more details
https://azure.microsoft.com/en-us/blog/azure-redis-cache-general-availability-of-premium-tier/ and https://azure.microsoft.com/en-us/documentation/articles/cache-how-to-premium-persistence/ -
Add Distributed Caching to Azure (i.e. like Velocity / memcached)
So that multiple web roles can share the same cache.
281 votesAzure now supports a family of distributed caches.
More details can be found at the Azure Cache home page – http://azure.microsoft.com/en-us/services/cache
-
Add support for AOF persistence or smaller RDB intervals
It should be possible to set a smaller interval for Redis snapshots (or a manually triggered one) and to choose between AOF or RDB or both for the persistence method.
264 votesRedis persistence is now available in the RDB as well as the AOF models. You can try out the AOF model today. AOF persistence is currently available as a Preview feature.
Here (https://docs.microsoft.com/en-us/azure/redis-cache/cache-how-to-premium-persistence#configure-aof-persistence) is some documentation about how to configure AOF persistence.
-
It should be possible to scale up pricing plan for Redis Cahce
In the portal today I can't scale up a Redis cache instanse. I'm stuck in Standard 250 MB and I want 1 GB. Does not seem to be possible.
My workaround now is to create a new redis cache with 1GB.
237 votesThis feature is now available. Please see this blog post for more details http://azure.microsoft.com/blog/2015/06/19/azure-redis-cache-updates-for-june-2015/
-
Update redis version
Current version is 3.0.0 while latest stable is 3.2.0.
There are big features which are missing like geo api and many more.
163 votes -
Add Redis Cache service support in Japan East/West Region
Not available cache service in Japan Region big opportunity loss. I no longer forced to use the East Asia bad latency.
155 votesWe now support Japan West and Japan East regions. Happy caching !
-
136 votes
Azure now supports a family of AppFabric (Velocity) based caches..
More details can be found at the Azure Cache home page – http://azure.microsoft.com/en-us/services/cache
-
Redis Cache should provide an Interface to test the Cache Failover capabilities
I wanted to test the Redis Cache Failover scenario (with Standard edition) for an enterprise application. But with current portal there are no ways we can test this capability.
Also would also like to test scenarios when one of the cache server is not performing well what are the heuristic defined for failing over to other node.
115 votesreboot has been on all tiers for a while now
-
Allow clustering of caches in different regions
Allow me to have Redis Caches in different regions and link them together in a bi-directional sync configuration so when you add something to the cache in one region, the data gets replicated to the other caches. This keeps the cache local and fast when you're running a site in multiple regions.
86 votesGeo-Replication is now available for use as a feature. It is released as a Preview at the moment. The replication is uni-directional at the moment.
Geo-replication provides a mechanism for linking two Premium tier Azure Redis Cache instances. One cache is designated as the primary linked cache, and the other as the secondary linked cache. The secondary linked cache becomes read-only, and data written to the primary cache is replicated to the secondary linked cache. This functionality can be used to replicate a cache across Azure regions.
Here is some more information: https://docs.microsoft.com/en-us/azure/redis-cache/cache-how-to-geo-replication.
We will continue to add more geo-replication scenarios. Please let us know what you’d like to see and in what priority order.
-
Support Redis Expire Keyspace Notifications
Receiving a callback when a key expires is currently not supported. Please add this as it provided a great way for handling session expiration.
82 votesThis feature is now available. Please see this blog post for more details http://azure.microsoft.com/blog/2015/06/19/azure-redis-cache-updates-for-june-2015/
-
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)
76 votesAzure Managed Cache service and Azure Redis Cache Preview, both support sharing of Cache across deployments.
-
Support hyphen in cache URL
Add support for using a hyphen in the URL for a redis cache instance. myapp-dev or myapp-test is much more aesthetically pleasing and easier to parse than myappdev or myapptest.
65 votesThis fix has been rolled out. You can now specify a name with a hyphen
-
Restart option for Azure Redis Cache
Currently I havn't seen any UI command to Restart Azure Redis Cache Service.
I know there is a way to shutdown and start however missing in the portal.59 votesThis is available now.
-
Make AppFabric Caching Support Notifications
AppFabric caching has quotas which cap the amount of traffic and number of transactions allowed. Without notification support Azure applications must poll to detect changes. This is veru undesirable.
43 votesAzure Managed Cache now supports notifications.
-
Add integration with V2 Virtual networks
Hello,
Right now we have integration between classic virtual networks and Redis Cache.
It's a very strong blocker for migration from classic to v2 model and also blocker if customer already using v2 infrastructure...37 votesWe are pleased to announce that this has now been enabled. Please see this service announcement for more details https://azure.microsoft.com/en-us/updates/azure-redis-cache-premium-tier-support-for-azure-virtual-network-v2-arm-based-virtual-networks/
-
Define ACL Rules for your Cache Instance
it would be great if we could further secure our Redis instance by defining the allowed IP addresses. Typically our cache is only accessed by our IIS application server therefore there is no need for the cache to be exposed to the public internet.
37 votesThere are various things you can do now. You can deploy your cache into a VNET and have NSG rules restrict the traffic to what is desired. Please ensure to look at this so that you enable access to the required ports (https://docs.microsoft.com/en-us/azure/redis-cache/cache-how-to-premium-vnet#what-are-some-common-misconfiguration-issues-with-azure-redis-cache-and-vnets).
You can also use the firewall feature to configure firewall rules to restrict access to only certain IP addresses. You might find this (https://docs.microsoft.com/en-us/azure/redis-cache/cache-configure#firewall) useful.
-
Enable firewall for all Azure Redis Cache dedicated service pricing tiers
Currently the Azure Redis Cache only allows the firewall to be set on premium pricing tiers. This security service should be available on all pricing tiers with a dedicated service
30 votesThis is now available on all pricing tiers.
-
Add Tags, Notifications, Regions to Azure Cache so that it is Usable
Without an ability to traverse collections of things the Azure cache is not very useful. Here's hoping they add notifications, regions, and tags.
29 votesAzure Managed Cache now supports the requested features.
-
[REQUEST] Please re-enable "retention" setting for Redis Cashe Diagnostics.
We can't configure "retention" for Azure Redis Cache Diagnostics right now, even though we were used to configure it from Preview Portal. Please re-enable "retention" setting so that we don't need to delete logs manually.
-Japanese-
Redis Cache の診断ログにおいて、以前はプレビューポータルからリテンションを設定することができましたが、現在は設定することができません。利用者が手動でログを削除する必要がないようにリテンションの設定を有効化してください。27 votes -
Allow different Storage Accounts for Diagnostics for separate Redis Resources in the same region
Allow different Storage Accounts for Diagnostics for separate Redis Resources in the same region
Currently, "Caches in the same region and subscription share the same diagnostics storage account, and when the configuration is changed it applies to all caches in the subscription that are in that region."
This is currently documented here: https://azure.microsoft.com/en-us/documentation/articles/cache-how-to-monitor/
This is a bad idea - I have different Applications and Resource Groups - with different Redis Resources.
I also like to keep my Diagnostics data separate, within an Application, but also across Applications.
Please allow me to assign different Storage Accounts for Diagnostics for Redis Resources…
23 votes
- Don't see your idea?